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 483342
To read all comments associated with this story, please click here.
Comment by Praxis
by Praxis on Wed 3rd Aug 2011 17:40 UTC
Member since:

Interesting benchmark. I'm glad that firefox is really making a push to take back the various performance crowns, and I hope that we do see some good gains out of it. But I still wonder if these improvements make that much of a difference to the average user. I know that some people always seem to pop up in browsers threads complaining that they have had 75 tabs open for 4 weeks and the performance is lousy so that means browser X sucks and for these users benchmarks like this are encouraging. But I know very very few people who actually use a browser like this. Is there a difference in performance with a more reasonable number of tabs, like 20 or so. And of course the big issue with firefox for me has always been memory leaks. Firefox has always beat the shit out of chrome is straight up open tabs and check memory usage. But in the real world your not just opening one set of tabs, your opening and closing them all day. And I have always found firefox to use more and more memory as the day goes on, while chrome keeps going back to the baseline memory usage. When Firefox fixes that memory problem I want to read a blog post on that.

Reply Score: 2