Linked by Thom Holwerda on Tue 12th Apr 2011 18:33 UTC
Permalink for comment 469964
To read all comments associated with this story, please click here.
To read all comments associated with this story, please click here.
News
Linked by Thom Holwerda on 05/23/13 23:22 UTC
Linked by Thom Holwerda on 05/23/13 22:04 UTC
Linked by Thom Holwerda on 05/23/13 22:01 UTC
Linked by Thom Holwerda on 05/23/13 17:52 UTC
Linked by Thom Holwerda on 05/22/13 22:23 UTC
Linked by Thom Holwerda on 05/22/13 13:38 UTC
Linked by Thom Holwerda on 05/22/13 13:30 UTC, submitted by JRepin
Linked by Thom Holwerda on 05/21/13 22:06 UTC
Linked by Thom Holwerda on 05/21/13 21:45 UTC
Linked by Thom Holwerda on 05/21/13 15:53 UTC
More News »
Sponsored Links



Member since:
2005-10-13
Most of the cases where Firefox is slower than IE in their demos has been shown to have nothing to do with hardware acceleration. It's nearly always slow javascript or DOM performance in some hotspot in the code that gets called 1000 times a second. For FF5 they added a little patch to cache 1 security check and ended up getting twice the performance of FF4 in some of those demos they were slow in, and there are lots of little performance bugs like that. They even forgot to turn on the profile-guided compilation for FF4, and switching that on bumped javascript performance by 10-15% without changing a line of code.
What IE has done really well is to create a bunch of demos, and then tune their browser around them. They've become the most common place to try out these new features, which means that because they tuned their browser against those tests they usually end up with an advantage. 3rd part tests would be much more fair, but at this point most people are just content to use the tests MS created.
Edited 2011-04-13 01:53 UTC