Google Chrome Benchmarks
So unless you've been living under a rock, you've probably heard about the release of Google Chrome. Being a hardcore Firefox nut myself, I'm not just skeptical, I'm largely indifferent. With Firebug, I've got the perfect web developer environment, so I'm good to go. It would be hard to sell me on something else.
Google is a buzzworthy company, though, and I've already heard from everyone and their mom about how simple, clean and (most notably), fast the browser is. This piqued my interest. Time for more benchmarks!
I really thought I'd published more benchmark articles by now, but there were only two, so amending them was quick and easy. Here are the results:
Try... Catch Benchmark
This benchmark was setup to see how quickly the standard browsers could execute code that was throwing (and catching) errors. Read the full article here.
| Browser | Solo | With try...catch |
With try...catch and an error |
|---|---|---|---|
| Firefox 2 | 36 milliseconds | 47 milliseconds | 32.917 seconds |
| Firefox 3 | 3 milliseconds | 4 milliseconds | 156 milliseconds |
| Google Chrome | 0 milliseconds | 6 milliseconds | 69 milliseconds |
| Internet Explorer 6 | 33 milliseconds | 35 milliseconds | 209 milliseconds |
| Internet Explorer 7 | 33 milliseconds | 35 milliseconds | 178 milliseconds |
| Opera | 6 milliseconds | 10 milliseconds | 3.011 seconds |
| Safari 3 | 13 milliseconds | 16 milliseconds | 50 milliseconds |
As you can see, Chrome is among the highest performers. It executes the plain code insanely fast (never more than 1 millisecond in any of my tests), and is only second to Safari 3 in terms of catching errors quickly.
Conditional Benchmarks
This benchmark is a little more abstract. The objective was to determine which conditional is fastest among if, switch and what I call an object conditional.
| Browser | if block |
switch statement |
object conditional |
|---|---|---|---|
| Firefox 2 | 444 milliseconds | 425 milliseconds | 310 milliseconds |
| Firefox 3 | 50 milliseconds | 38 milliseconds | 42 milliseconds |
| Google Chrome | 11 milliseconds | 11 milliseconds | 20 milliseconds |
| Internet Explorer 6 | 353 milliseconds | 347 milliseconds | 290 milliseconds |
| Internet Explorer 7 | 375 milliseconds | 381 milliseconds | 344 milliseconds |
| Opera 9.5 | 50 milliseconds | 55 milliseconds | 54 milliseconds |
| Safari 3 | 150 milliseconds | 156 milliseconds | 137 milliseconds |
Turns out, that was no fluke earlier. Chrome easily blows away the competition here. I might question Google's motives (and I certainly think it's a tad shady to have renewed their contract with their now-competitor and then release competing software), but I applaud their speed of my beloved JavaScript.
I tried
http://nontroppo.org/timer/kestrel_tests/
Chrome came out neither fastest nor most memory efficient.
[...] had enough time to test this thoroughly, but the folks over at scriptNode have put together some benchmarks and it seems that Chrome not only handles good code well, it also excels at handling [...]
[...] had enough time to test this thoroughly, but the folks over at scriptNode have put together some benchmarks and it seems that Chrome not only handles good code well, it also excels at handling [...]
[...] had enough time to test this thoroughly, but the folks over at scriptNode have put together some benchmarks and it seems that Chrome not only handles good code well, it also excels at handling [...]
Every browser team is working on faster JavaScript now. Try the current alpha version of Firefox 3.1.
See http://weblogs.mozillazine.org/roadmap/archives/2008/09/tracemonkey_update.html for some numbers.
Remember: Chrome is “just” a beta version with its own flaws and shortcomings.
Why do you think it’s shady that google still supports Mozilla/FF? I’d think you’d be grateful that they decided to support both. On mashable or so someone pointed out that better browsers, and more competition kinda improve the internet as a whole, and that’s good for google and the areas of the company that actually make money.
[...] Handles code and errors very well. Benchmarks here. [...]
@flo: Typically Google had been signing two-year contracts with Mozilla. Just a week before announcing Chrome, they signed a three-year contract (a move Mozilla said was “unexpected”). It seems like this buys them time. Once the contract expires, if Chrome was a success they can opt out of renewing the contract. Otherwise, they can renew it. They’re treating Mozilla like a fallback instead of a partner, like they had previously.
I’m not going to pretend like I know exactly what they’re up to, but it feels shady to me.
http://www.techcrunch.com/2008/09/03/mozilla-fights-back-with-new-firefox-benchmarks/
They’re not competing. Firefox is free to use any of Chrome’s code.
[...] had enough time to test this thoroughly, but the folks over at scriptNode have put together some benchmarks and it seems that Chrome not only handles good code well, it also excels at handling [...]
Nice try, but Chrome was several times faster than any other browser on those benchmarks. Mozilla shill.
“I tried
http://nontroppo.org/timer/kestrel_tests/
Chrome came out neither fastest nor most memory efficient.”
[...] ScriptNode.com [...]
[...] Hackett also published a [...]
I’m sure the big G is in bed with Mozilla for many good reasons, and one of them will be “the enemy of my enemy is my friend”.
Maybe Google isn’t after becoming the dominant browser yet. Perhaps this is just a ‘Google client’ built to give their web apps an edge and they’d expect any right-thinking geek to carry on using a mainstream browser for the other stuff..
[...] the fact that it’s still in Beta (aren’t most Google products? ex. Gmail) it has been benchmarked by geeks on scriptNode as the fastest browser on the [...]
Not all code runs faster in Chrome. There is a new benchmark here http://www.wrensoft.com/forum/showthread.php?t=2789 with Firefox coming out on top. IE is still looking pretty sad however.
[...] reliable and organized browsing experience. Google Chrome is fast, just check out the benchmarks here there and [...]
I just saw this: http://www.wrensoft.com/forum/showthread.php?t=2789
Obviously Chrome can’t be better at everything, and in this case, it’s Firefox that’s the winner. What’s funny is just how bad IE is compared to these two.
Congrats. You just made it on my ‘Respect’ tab in Google Reader.
I agree with you, I can’t see life without Firebug and until Webkit get’s something almost identical (or Webkit Inspector gains all the missing amenities that make using Firebug a charm) I’m sticking with the flaming fox.
The speed is amazing though…
By now the IE guys must be under the gun. They have the slowest pos on the market and should really abandon jscript, adopting one of the other options, and just keep focused on making the rest of their browser better.
Please add Internet Explorer 8 beta to the test.
[...] http://scriptnode.com/article/google-chrome-benchmarks/ [...]
[...] has subjected chrome to an even more in-depth battering of 6 different benchmark tests which i’m not going to replicate here cos i’m not big enough a geek. all you need to [...]
[...] had enough time to test this thoroughly, but the folks over at scriptNode have put together some benchmarks and it seems that Chrome not only handles good code well, it also excels at handling [...]
The guys that do TinyMCE (the richtext editor) just did some real-world browser performance tests, too. Pretty similar stuff:
http://blog.moxiecode.com/2008/09/04/browser-performance-chrome-compared/
[...] to be really fast. It starts up fast, shows pages quickly and executes Javascript quickly (see some benchmarks at scriptNode). What I also love is that one slow site doesn’t hang your whole browser. For example if you [...]
And its windows only
[...] Recent public urls tagged “benchmarks” → Google Chrome Benchmarks [...]
Chrome has some nice features, but after a few hours with it, I’ve found it quite laggy in places – not a Firefox replacement for sure.
[...] had enough time to test this thoroughly, but the folks over at scriptNode have put together some benchmarks and it seems that Chrome not only handles good code well, it also excels at handling [...]
i am download from official website GChrome.
i am aware:
Malware include.
GoogleUpdater.exe (trojan.generic)
its running auto in process.
its just my problem or …..!!!
sorry , my English is bad.
[...] untuk link web yang menampilkan pengetesan googleChrome secara statistik klik disini. [...]
[...] (Kecepatan menampilkan hasil pencarian dan meload seluruh halaman suatu web.) untuk link web yang menampilkan pengetesan googleChrome secara statistik klik disini. [...]
Hello webmaster
I would like to share with you a link to your site
write me here preonrelt@mail.ru