Warning: file_get_contents() [function.file-get-contents]: php_network_getaddresses: getaddrinfo failed: Name or service not known in /home/thechro2/public_html/wp-content/plugins/digg-digg/include/dd-class.php on line 1202
Warning: file_get_contents(http://feeds.delicious.com/v2/json/urlinfo/data?url=http%3A%2F%2Fwww.thechromesource.com%2Fvideo-chrome-6-vs-chrome-7-with-hardware-acceleration%2F) [function.file-get-contents]: failed to open stream: php_network_getaddresses: getaddrinfo failed: Name or service not known in /home/thechro2/public_html/wp-content/plugins/digg-digg/include/dd-class.php on line 1202
Just so that we all know that hardware acceleration in Chrome 7 isn’t some fancy pipe dream, I decided to test it out using Microsoft’s FishIE Tank test which measures the frame rate that a browser can load a tank full of fishes.
I used the latest beta of Chrome 6 and the latest Canary version of Chrome 7 with the command line switch “–enable-accelerated-compositing” which turns on GPU processing. Neither of the browsers had any extra extensions installed.
It’s interesting to see how wacky the hardware acceleration causes the framerate to be in Chrome 7. It suggests to me that there is still some work to be done on this early version. While it’s clear that Chrome 7 has a better frames per second rate, Chrome 6 is able to provide a more consistent level of performance even though the rate is much lower.
Of course, it’s been warned for some time that Canary will always be less stable, and using command line switches within it are even less so. You can do your own browser testing if you’d like to with all of Microsoft’s tests here.