Skip to main content

Firefox 4 beta 5 is out, hardware acceleration enabled by default

And it still isn't fast enough. I made a little experiment by checking the IE 9 platform preview, the Firefox 4 beta 5 and the Google Chrome 7.0.503 dev with a Microsoft benchmark that was designed to show off IE9's new (back then) hardware acceleration features: Psychedelic Browsing. My results were, well, not what I expected:
I mean, I knew that IE 9 would score fine, but I can't believe that Chrome did so badly. And yes, the GPU process for Chrome is clearly running. Can we even bitch about the benchmark not being fair?

Update: I have tried this on the Chromium nightly build 58924 and it scored 10, and also saw some claims online that not all of the GPU acceleration for Chromium is up and running yet.

Update #2: I have also tried this on the Minefield nightly build, beta 6, and it scored 680, with IE 9 scoring 829 and Chrome dev a really shitty 10. I would love to know why the IE 9 score varies so wildly. 

Comments

Popular posts from this blog

On sleep deprivation and Incan Monkey Gods

From: Dilbert comic strip for 08/03/1992 from the official Dilbert comic strips archive. I was trying to show this strip to a coworker who is dangerously toying with the harsh mistress that is Insomnia. What shocked me is how quickly I was able to look up the strip, which was published when he was just 11 years old, and two weeks before my just-out-of-college ass shipped out to US Army Basic Training.

The Black Hole

If this was a minigolf hole, you can't reach B from A. Ever. If this was a room lined with mirrors, and you lit a candle at point A, you can't see it from B, not even reflected.  Update: I guess I didn't explain this all the way through. You can't reach B from A with just one stroke, there's no direct line between them, and there is no way to bounce the ball (assuming perfect conditions). Thanks to Ben for pointing this obvious error. 

Add custom speed settings to your ifit map workout

Ifit.com allows you to build a workout walk/race/bike route simply by clicking on a Google Maps interface. You can then use a compatible ifit-enabled workout machine to recreate the route automatically. The problem is that the user interface still isn't final, so there are features in place that aren't exactly obvious. For example, if you create a workout your machine starts at 1 MPH, because that's the default. But how to set it to start at say, 3 MPH? Easy, just switch from map view to graph view: That button switches from the Google Maps interface to a chart that allows you to visualize and control effort: You can't change the elevation, this is fixed due to the geography that you selected. But you can drag the yellow (speed line) to change the speed of your device.  What if you want to have segments at different speeds? Easy, just click and drag and it will break the line, and you can drag each segment of the line independently: ...