Mozilla Rechallenges Google in Browser Speed Race

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.

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

Wolfgang Gruener
Contributor

Wolfgang Gruener is an experienced professional in digital strategy and content, specializing in web strategy, content architecture, user experience, and applying AI in content operations within the insurtech industry. His previous roles include Director, Digital Strategy and Content Experience at American Eagle, Managing Editor at TG Daily, and contributing to publications like Tom's Guide and Tom's Hardware.

  • 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?

    Nevertheless, it would be nice of Mozilla to iron out any bugs. That includes you, Adobe.
    Reply
  • 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
  • If only Mozilla would move into the 21st century with a 64 bit Windows version...
    Reply
  • azathoth
    Scoring 2150ms using the firefox nightly (v17) on my PC here.
    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.

    And for your information, I gave Beta a try. The problem also exists.
    Reply
  • 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
  • mmstick
    Mozilla DOES have a 64-bit firefox. It's called waterfox. http://waterfoxproject.org/
    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