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.
Permalink for comment 483615
To read all comments associated with this story, please click here.
RE[2]: Not a very good test
by renox on Thu 4th Aug 2011 12:26 UTC 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