Firefox, Chrome virtually tied for JavaScript speed
Google's Chrome now is only a smidgen slower than Mozilla's Firefox on the SunSpider test of JavaScript.
(Credit: CNET News)On Tuesday, Mozilla released Firefox 3.1 beta 2 and Google released Chrome 0.4.154.33, so it's time for the latest installment of JavaScript performance testing.
Here's the highlight: Though Firefox remains the leader on the SunSpider test, with a score of 2,110, Chrome edged very close with 2,140. A lower score is better; because of some variation in results, the numbers I quoted are an average of several runs.
Firefox and Chrome aren't the only browsers out there, but they're interesting to compare for a few reasons. First, they're both open-source projects launched to shake up the establishment with new ideas about the browsing experience. Second, given that philosophical alignment, they're likely to appeal to the same early-adopter crowd. Finally, both have new JavaScript engines, Chrome's V8 and Mozilla's TraceMonkey, which in the new beta is switched on by default.
JavaScript is used to build sophisticated Web sites such as Gmail or Google Docs, but it's also widely used for more ordinary operations, so faster JavaScript performance is desirable. One interesting possibility Google has raised for Web applications though is to bypass JavaScript altogether and use Google's new Native Client software, a research project that lets Web-based software run closer to the speeds of regular software on a computer.
Chrome is making steady gains in Google's JavaScript test; Firefox is much slower and has a mixed record.
(Credit: CNET News)SunSpider is only one test, though; Google has its own JavaScript benchmark on which Chrome wins hands-down. A glitch in the first Firefox beta kept me from testing it on Google's benchmarks, but the new beta runs again, yielding a score of 182. That's lower than the earlier Firefox 3.1 beta's 235 score, so perhaps something is still amiss. Either way, it's a far cry from Chrome 0.4.154.33's score of 2,635.
The usual caveats: your mileage may vary; I ran these tests on a dual-core Lenovo T61 laptop with 3GB of memory and Windows XP. JavaScript is only one aspect of Web browsing performance, and indeed of browsers overall. Also, this software is still in beta, Chrome in particular a developer beta. Finally, I apologize to those who've been asking, but time constraints have kept me from trying the latest WebKit builds and Opera.
According to Mark Larson, Google's Chrome program manager, Chrome 0.4.154.33 fixes a crash when opening the Options dialog box on 64-bit Windows and some issues using Hotmail. "Hotmail still does not properly recognize Google Chrome," though, Larson said in his announcement of the new version, though it can be fooled into thinking it's using a more mainstream browser. For details, check the instructions on the release notes.
Stephen Shankland writes about a wide range of technology and products, but has a particular focus on browsers and digital photography. He joined CNET News in 1998 and since then also has covered Google, Yahoo, servers, supercomputing, Linux and open-source software, and science. E-mail Stephen, or follow him on Twitter at http://www.twitter.com/stshank. 




You may find that WebKit is even faster than Chrome and FF3.1b, which bodes well for future releases of Safari (and possibly Chrome).
Just leave Safari out of the comparison if you're not going to update it!
Also, a minor quibble. When you have a separate bar for each version of the browsers, can you put the name of the version right inside the bar? Hard to reconcile all the bar colors with the different browsers.
With their slower clock speeds and Internet Explorer crashing so often, these pc's were quickly becoming the bane of my existence.
Not any more.
For every release where Chrome gets better - Windows is fading farther and farther into the background - where it belongs. I always felt it was a shame to spend top-dollar on IBM Thinkpads, only to saddle them with a turkey of an operating system.
Now - I find myself forgetting that I'm even running Windows - and I'm reconsidering my decision to dump this older gear.
Not bad for a free browser.
Rob
My goal is to use less and less Windows-supplied products as I move forward. Since I don't have the time and energy to move to Linux - this provides my way forward.
You are correct - Chrome still runs on Windows - but Chrome dispenses with 90% of my actual system crashes (as probably Firefox et al would as well). Many times I can't even get windows to terminate a balky IE session gracefully without repeatedly hitting "End Now" and seeing multiple Windows system responses to such efforts.
Moving to Chrome effectively allows me to take one big step away from the annoying Windows experience - no doubt about it.
As I do not agree with Microsoft's design philosophy of bloated products (and bloated methods of dealing with their misbehavior) - replacing Windows applications (from Word to IExplorer) one-by-one over time - effectively reduces my involvement with Windows.
Recently I've moved from Hotmail to Gmail, from IExplorer to Chrome, and eventually I hope to move from Office to Google's or IBM's new web-based office-offerings.
I expect all of these to be less bloated, more friendly and hopefully more stable. We'll see. If so - then Windows inherently will present a more stable - and less intrusive - user experience for me.
This is why I refer to Windows as "fading" into the background - and not "disappearing".
Whether or not all these new products prove less bloated, and more stable, only time will tell.
So my goal of using less Windows products - while still running Windows - will hopefully allow me to achieve greater system stability and ease of use.
By 'WIndows' product do you mean 'Microsoft' product? Windows is the environment, Microsoft is the company. Companies create products. Environments are where those products are run.
Next time, I might read your comments if use one every now and then.
Well, here's what it would've looked like.
http://www.favbrowser.com/performance-firefox-vs-safari-vs-google-chrome-vs-opera/
And note that Opera's MAMA shows that ~3.5% of the web use XMLHttpRequest.
http://dev.opera.com/articles/view/mama-key-findings/#xmlhttprequest
I dont have the energy or time to mess with windows operating system disinfecting it after infected with its trogens, virii, worms, malware. Yes all stick to Novell's Suse Desktop Enterprize for my Tower. much more reliable then windows.
Bias Bias Bias. Screw google an use the scroogle scrapper at http://www.scroogle.org/cgi-bin/scraper.htm
Safari 3.2.1 the current release (3.1.2) result = 2678.6ms
Camino 1.6.5 = 8770.6
Webkit daily build (12/08/08) = 707.8 yes! really fast!!
On a battery of tests , Chrome was faster by far. Cnet is for amateurs.
See my post above regarding how Chrome single-handedly made me reconsider dumping out my older, slower (but much beloved) Thinkpads.
After years of being flummoxed by endlessly bloated software products from you-know-who, we're finally getting some alternatives here - and Chrome is the reason.
My old Thinkpads are faster, more stable and fun to use like never before because of this product. Can't wait to try Google's web-based office apps on Chrome too.
I've been in IT for 30 years (applications developer - financial services) and am completely fed-up with needless product complexity & dubious "features" - designed from the get-go by Microsoft - just to upstage the competitor's products using a bunch of flashy song & dance routines.
Rob
- by Jyakotu December 11, 2008 7:11 AM PST
- Opera's JavaScript speed is not an issue with me. It still preforms JavaScript pretty fast IMO. I can tell the speed improvements with a Opera 10.00 Alpha 1 build.
- Reply to this comment
-
Showing 1 of 2 pages (31 Comments)