Linked by David Adams on Wed 3rd Aug 2011 16:50 UTC, submitted by _xmv
Mozilla & Gecko clones Mozilla Firefox has been listening to recent memory complains, and as a side effect tested the browser's scalability to the extreme with memshrink's improvements. The results are shocking: For 150 tabs open using the test script, Firefox nightly takes 6 min 14 on the test system, uses 2GB and stays responsive. For the same test, Chrome takes 28 min 55 and is unusable during loading. An optimized version of the script has been made for Chrome as an attempt to work-around Chrome's limitations and got an improved loading time of 27 min 58, while using 5GB of memory.
Thread beginning with comment 483580
To read all comments associated with this story, please click here.
Not a very good test
by renox on Thu 4th Aug 2011 09:08 UTC
renox
Member since:
2005-07-06

So OK, FF is better than Chrome if you open 150 tabs simultaneously, but who does that??
Nobody: you open tabs, close some, open other, etc and in the end you may have a big number of tabs open (though 150 seems excessive to me: 50 would be more interesting).

This would be a better test, and the results may be different: the architecture of Chrome may allow better resource management than thread oriented FF..

Also he should try his benchmark with different settings: it's possible to configure Chrome to use only one process, I wonder if the resource usage would be very different..

Reply Score: 2

RE: Not a very good test
by oskeladden on Thu 4th Aug 2011 09:24 in reply to "Not a very good test"
oskeladden Member since:
2009-08-05

*Ahem* Not quite 'nobody'. My wife had 173 tabs open in Firefox last evening. I don't think she's the only one in the world to open that many tabs.

Reply Parent Score: 1

RE: Not a very good test
by Phucked on Thu 4th Aug 2011 09:58 in reply to "Not a very good test"
Phucked Member since:
2008-09-24

I have a 112 tabs open in Firefox right now!

On some days I have over 400 tabs open in about 20ish browser windows spread out over IE9, FireFox 6 beta, and Chrome 13 beta running at the same time under windows.

Right now I am running Slackware, I have those 112 tabs on firefox plus about 30 rekonq tabs, and about 80 tabs open in Opera.

I am just a ocd power user!

Edited 2011-08-04 09:59 UTC

Reply Parent Score: 3

RE: Not a very good test
by Erunno on Thu 4th Aug 2011 10:20 in reply to "Not a very good test"
Erunno Member since:
2007-06-22

This would be a better test, and the results may be different: the architecture of Chrome may allow better resource management than thread oriented FF..


I cringe every time process separation is mentioned as a mean of resource management. It actually is only useful to hide inefficiencies by hoping that the process will be shut down before its resource usage causes noticeable problems. I'd rather have the browser developers discover and fix memory leaks and optimize their data structures before relying on such heavy-handed "solutions".

Reply Parent Score: 2

RE[2]: Not a very good test
by renox on Thu 4th Aug 2011 12:26 in reply to "RE: Not a very good test"
renox Member since:
2005-07-06

I cringe every time process separation is mentioned as a mean of resource management.


Oh really? So explain to me: how do you know which tab use 99% of CPU/too much memory in Firefox?
With Chrome it's easy: it has an integrated "task" manager.

Look: the default "share nothing" of processes is much better from a security, resource management POV than "share everything" of threads: threads are an optimisation, that's all.

Reply Parent Score: 2