Linked by Thom Holwerda on Thu 23rd Sep 2010 21:36 UTC, submitted by google_ninja
Internet & Networking Now this is a subject sure to cause some discussion among all of you. LifeHacker's Adam Pash is arguing that Chrome has overtaken Firefox as the browser of choice for what he calls 'power users'; polls among LifeHacker's readership indeed seem to confirm just that. He also gives a number of reasons as to why this is the case.
Thread beginning with comment 442413
To view parent comment, click here.
To read all comments associated with this story, please click here.
Neolander
Member since:
2010-03-08

One thing to note though is that the Firefox guys consistently show benchmarks of their latest code against stable, released versions of other browsers. If you filter out the drumroll what's left is a claim that says the browser we are going to realease will be as fast as the browser you have released months ago.

Wrong. Hover the graphs. They use latest builds of safari and chrome (or nitro and V8 if you want).

As of now, Chrome runs circles around Firefox in various performance benchmarks. Try peacekeeper, for instance: google "peacekeeper browser benchmark" - FF on my system gets 36xx score while Chrome gets 9001! We have this

We all know that FF is currently a bit slow. The question is, will FF4 be back among the others ? It seems that it might be the case. And the worst is that in the end, it does not matter : as a user, what's most important is not page rendering speed, it's UI responsiveness, and no benchmark currently measures this. E.g : IE7&IE8 take several seconds to open a tab when under load, FF3.5 was about as bad, though a bit faster (don't remember about 3.6), and on all other browsers the process is instant.

Edited 2010-09-24 06:23 UTC

Reply Parent Score: 2

Fergy Member since:
2006-04-10

"One thing to note though is that the Firefox guys consistently show benchmarks of their latest code against stable, released versions of other browsers. If you filter out the drumroll what's left is a claim that says the browser we are going to realease will be as fast as the browser you have released months ago.

Wrong. Hover the graphs. They use latest builds of safari and chrome (or nitro and V8 if you want).

As of now, Chrome runs circles around Firefox in various performance benchmarks. Try peacekeeper, for instance: google "peacekeeper browser benchmark" - FF on my system gets 36xx score while Chrome gets 9001! We have this

We all know that FF is currently a bit slow. The question is, will FF4 be back among the others ? It seems that it might be the case. And the worst is that in the end, it does not matter : as a user, what's most important is not page rendering speed, it's UI responsiveness, and no benchmark currently measures this. E.g : IE7&IE8 take several seconds to open a tab when under load, FF3.5 was about as bad, though a bit faster (don't remember about 3.6), and on all other browsers the process is instant.
"
A lot of effort has gone into making startup and shutdown faster. Also extension updates have been optimized. The main advantage of Chrome is the multiprocess stuff that really takes advantage of multiple cores and makes sure that the GUI never slows down. I hope Firefox 4.1 will introduce multiprocess.

Reply Parent Score: 1

molnarcs Member since:
2005-09-10

Link please - the initial press release featured static benchmarks. I don't know which benchmark page you are referring to. I googled kraken benchmark, found this on tested.com:
http://www.tested.com/news/which-web-browser-can-best-mozillas-new-...

As I expected, even Chrome 6.xxx seems to beat FF 4 in speed.

Reply Parent Score: 2

smitty Member since:
2005-10-13

He's probably talking about JM, which wasn't included in beta 6 but will be in 7. Here are some numbers from arewefastyet.com (take with a grain of salt, of course) http://arewefastyet.com/kraken_temp/.

I'm not sure those results really make sense to me. Benchmarks of FF4 should probably wait until JM is actually released in a working beta, at this point testing the nightlies is too fluid to get good results and the old betas aren't at all representative of what FF4 will be like.

It would also be good to have an expert breakdown of the kraken benchmark to tell us what it's testing. For example, is everything really blocked on javascript performance, or is it also testing the speed of the audio tag for those tests, and other DOM stuff.

Edited 2010-09-24 08:43 UTC

Reply Parent Score: 2

lemur2 Member since:
2007-02-17

Link please


http://arewefastyet.com/

I don't know which benchmark page you are referring to. I googled kraken benchmark, found this on tested.com:
http://www.tested.com/news/which-web-browser-can-best-mozillas-new-...

As I expected, even Chrome 6.xxx seems to beat FF 4 in speed.


That testing was for Firefox 4 Beta 6.

Firefox 4 Beta 6 doesn't include Jaegermonkey, it includes only Tracemonkey.

http://arewefastyet.com/

The gold plotline is "moz TM" ... Tracemonkey. This is what you will get in Firefox 4 Beta 6.

The black plotline is Jaegermonkey alone. The purple plotline is Jaegermonkey + Tracemonkey. The latter is what will go in Firefox 4.0 final release.

On Sunspider, Jaegermonkey + Tracemonkey = 430, Tracemonkey alone = 538.

This is a 25% improvement over Firefox 4 Beta 6.

On v8bench, Jaegermonkey + Tracemonkey = 2684, Tracemonkey alone = 5080.

This is a 90% improvement over Firefox 4 Beta 6.

Edited 2010-09-24 11:29 UTC

Reply Parent Score: 2