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 483593
To read all comments associated with this story, please click here.
RE: Not a very good test
by Erunno on Thu 4th Aug 2011 10:20 UTC 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