Mozilla Rechallenges Google in Browser Speed Race
The browser speed war appeared to be pretty much over, until a few days ago, when Mozilla's JIT compiler lead David Mandelin sent out a tweet that the new JIT IonMonkey has eclipsed Chrome in at least one configuration on Mozilla's Kraken benchmark.
Posted on Mozilla's AreWeFastYet page - which was originally established when Mozilla began working on JaegerMonkey (that arrived with Firefox 4 and is still in use today) - Firefox 17 with IonMonkey squeezes the win with a performance of 1991 ms versus Chrome's 2038 ms. Mandelin notes that this result is achieved on a Mac Pro with a 32-bit version of the browser.
Of course, JavaScript benchmarks were interesting two years ago and it seems we have largely lost interest in the millisecond race, but I was nevertheless interested in those claims. In the end, Mozilla promised in 2009 that it would try to catch up with Chrome and if it can do it now, even if it is a bit late, it's noteworthy since it kept its promise.
I was not able to replicate the claim on my venerable Phenom II X6 Windows 7 system. Chrome won with 3349 ms versus 3715 ms for Firefox. However, IonMonkey gained almost 20 percent of speed over the current JaegerMonkey in Firefox 15 beta, which came in at 4627 ms. Perhaps there is still some room left for faster JavaScript engines?
Contact Us for News Tips, Corrections and Feedback
Stay On the Cutting Edge: Get the Tom's Hardware Newsletter
Get Tom's Hardware's best news and in-depth reviews, straight to your inbox.
30-year-old Pentium FDIV bug tracked down in the silicon — Ken Shirriff takes the microscope to Intel's first-ever recall
Cyberpunk 2077 update 2.2 claims to improve Arrow Lake performance by up to 33%, theoretically matching the Ryzen 7 7800X3D
Empyrean Technology gives control to CEC after U.S. blacklisting — China’s top developer of chip design systems hands reins to state-owned firm
-
A Bad Day I'm currently using Firefox Aurora, and it has a crashing/lock-up problem with Flash 11.3 since the two or three previous versions ago. Did they iron it out in Beta?Reply
Nevertheless, it would be nice of Mozilla to iron out any bugs. That includes you, Adobe. -
carnage9270 About as useful as a poopie-flavored lollipop. The browser wars were over long ago. I guess it's all about the nostalgia?Reply -
Kodiack @A Bad Day: Funny, I use both Chrome and the Firefox Nightly build and I'm stable as a rock. Also, you're also on a non-release build. What do you think that's for, if not ironing out bugs?Reply -
livebriand I'd mainly like to see them work on making the UI faster - Firefox's benchmarks don't mean shit when the browser constantly freezes on my E350 machine. (Chrome is completely smooth, in comparison.)Reply -
A Bad Day Kodiack@A Bad Day: Funny, I use both Chrome and the Firefox Nightly build and I'm stable as a rock. Also, you're also on a non-release build. What do you think that's for, if not ironing out bugs?I become somewhat worried if a problem also existed in version 15 and maybe even 14.Reply
And for your information, I gave Beta a try. The problem also exists. -
tomfreak The speed diff is not really an issue anymore. Both browser are fast enough. What I really need is the browser that push more usage on hardware GPU acceleration. DX10/11 GPU are pretty common these days, get someone to put serious effort in GPGPU computing. At least those Atom/E-350 user get better browsing experience.Reply -
bustapr instead of making it faster, they should work on making it more stable. i use firefox most of the time, and every time I load a page my entire browser locks up for like 2 seconds...Reply