Web Browser Grand Prix 3: IE9 Enters The Race
-
Page 1:Introduction
-
Page 2:Getting To Know Internet Explorer Again
-
Page 3:Test System Specs And Setup
-
Page 4:Performance Benchmarks: Startup Times
-
Page 5:Performance Benchmarks: Page Load Times
-
Page 6:Performance Benchmarks: JavaScript
-
Page 7:Performance Benchmarks: Peacekeeper, Dromaeo DOM, And Acid3 Speed
-
Page 8:Performance Benchmarks: HTML5
-
Page 9:Performance Benchmarks: Adobe Flash
-
Page 10:Performance Benchmarks: Java And Silverlight
-
Page 11:Efficiency Benchmarks: Memory Usage And Management
-
Page 12:Compliance Benchmarks: HTML5, CSS3, JavaScript, And Acid3
-
Page 13:Final Results: Placing
-
Page 14:Conclusion
Performance Benchmarks: HTML5
Internet Explorer enters the HTML5 competition for the first time with its latest iteration.
GUIMark 2: HTML5 Vector Charting (2 pixels)
This is the original two-pixel version of the GUIMark 2 HTML Vector Charting benchmark.
Opera excels in this test, scoring nearly 35 FPS. The new IE9 achieves a respectable 22 FPS, while Firefox finishes third with 21. Chrome flounders in fourth, achieving just under eight frames. As reported, Safari stutters in this variant of the HTML5 vector charting test, coming in last with only five and a half frames per second.
GUIMark 2: HTML5 Vector Charting (1 pixel)
This is the single-pixel variant of the GUIMark 2 HTML5 Vector Charting test. The original two-pixel version is reported to have trouble in Safari.
Opera again takes the gold with roughly 35 FPS. Safari shoots up to second place with a score of nearly 30 frames per second. Internet Explorer 9 places third with a slight boost of 1.5 FPS from the two-pixel results. It appears Safari isn't the only Web browser to benefit from the switch to single-pixel; Firefox and Chrome score much better as well. Firerfox reaches just over the 20 FPS mark, while Chrome is just under.
GUIMark 2: HTML5 Bitmap Gaming
IE9 absolutely murders the rest of the pack in this test, scoring just shy of the vaunted 60 frames per second. Google Chrome places second with 36 FPS. Opera grabs third place, with just under 20 frames, while Safari achieves half that score. Again in last place, Firefox receives a score of only seven frames per second.
GUIMark 2: HTML5 Text Column
Microsoft's new entrant into the WBGP again stomps the competition in HTML5 with nearly 52 FPS. Firefox comes in second, yielding just under 40 FPS. Opera, Safari, and Chrome fill out third, fourth, and fifth place, all coming in around 30 FPS.
- Introduction
- Getting To Know Internet Explorer Again
- Test System Specs And Setup
- Performance Benchmarks: Startup Times
- Performance Benchmarks: Page Load Times
- Performance Benchmarks: JavaScript
- Performance Benchmarks: Peacekeeper, Dromaeo DOM, And Acid3 Speed
- Performance Benchmarks: HTML5
- Performance Benchmarks: Adobe Flash
- Performance Benchmarks: Java And Silverlight
- Efficiency Benchmarks: Memory Usage And Management
- Compliance Benchmarks: HTML5, CSS3, JavaScript, And Acid3
- Final Results: Placing
- Conclusion
but there is no mention of any addon/extentions for IE..
i mean there is no comparision on who's got nice addons and startup time "with" addons.. since users tend to use web browsers with addons knowingly or un-knowingly..
it would be better if you include those two comparisions as well.. and who takes advantage of GPU and all..
lol
maybe not!!
and FFS why doesnt that "submit my comment" button not working in IE!! I am using chrome for that ;(
Then they would have to include every random nightly build of every browser? Comparing the latest release is fair you'll always get one browser or two that is near a new stable version but that's just how it works.
depends in Microsoft moves up an update schedule that doesn't just include making the browser more secure and fixing bugs. IE8 was pretty snappy back when it was first out it got old in like 3 months compared to other browsers though.
We only test final products in the WBGP.
Where are ya'll getting a set date from?
We add/modify tests every time with the WBGP. We're already looking into those suggestions.
Doh! Fixing that now.
http://groups.google.com/group/mozilla.dev.planning/browse_thread/thread/d7cd3c9e9650b1b3
(I'm assuming they tested the Windows version of Safari, because why would you compare browsers for different systems?)
I'm sticking with Opera on my Windows machine and Safari on my Mac.
http://www.theregister.co.uk/2011/03/16/mozilla_ship_firefox_4_22_march/
Although most websites link to this website, so perhaps it was nothing more than a rumor.
Opera sucks balls in memory management and lacks handy add-on such as Tab Mix Plus (which is same for Chrome). I would definitely move to Opera if it has these 2 issues fixed.
This article looks like a case of premature e.. something.
On the 16th he said RC1 would become the final code on the 22nd, but they released an RC2 since. I don't believe them anymore. Where is an official announcement or press release? RC1 was supposed to be here in November 2010. WBGP3 was going to feature FF4 at the end of 2010, then again at the end of this Feb. IE9 gave a date, so WBGP3 was made to coincide with its release. IF Firefox 4 launches tomorrow, it's purely coincidental. We stopped holding the WBGP series up for FF4 when MS officially gave their IE9 release date.