3-way hardware-accelerated browser shoot-out: Chrome on top, IE9 just behind and Firefox brings up the rear (video)
That speed comes at a price! As I discuss in the video, Chrome might be faster, but it uses significantly more resources than either IE9 or Firefox 4. Firefox is some 30% slower, but at the same time seems to use less CPU and GPU time. IE9 seems to utilize the same amount of CPU time as Chrome, but a little less of the GPU -- and it's marginally slower as a result.
What I don't know is whether this is by design or not. You'll notice that the GPU never went far above 50% -- why, with three browsers open, does it not get closer to 100%? The resources are there to be used -- why not use them?! Likewise, my CPU is still only half-used even when all three browsers are drawing 1000 frantic fishes at the same time. If you're curious, the other IE9 test drive samples all provided similar results. I wanted to try Google's 'HTML5 rocks' sample gallery, but they intentionally used elements of CSS and HTML5 that aren't yet supported in Internet Explorer 9 or Firefox 4.
In the name of science, here's some more information about my process: the screen capture does slow down each browser by a few frames per second, but relatively the figures are still accurate. I saw a small deviation in FPS when I was only running one browser at a time (probably because my CPU has multiple cores). There are a few unknown variables too, like whether the CPU core usage is defined by the app, or by the operating system (but with Chrome using more resources than IE9, you can only assume that Windows isn't unfairly biasing its own-brand browser).
If you'd like to recreate my test, you'll need to enable hardware acceleration in Firefox 4 and Chrome -- IE9 has it turned on by default:
- Firefox 4 -- grab a nightly build, navigate to about:config and add gfx.font_rendering.directwrite.enabled -- set it to 'true'
- Chrome 7 -- grab a nightly build and add the following flags to the shortcut before opening it: --enable-accelerated-compositing --enable-gpu-plugin --enable-gpu-rendering --enable-accelerated-2d-canvas