3 ms·
That's certainly what I did. Firefox has improved immeasurably (at least for me) since about version 14, while Chrome has crept up in size. As a point of refere
by sliverstorm 13y ago
That's certainly what I did. Firefox has improved immeasurably (at least for me) since about version 14, while Chrome has crept up in size. As a point of reference, if I open one tab in Chrome with Google Music and I let my computer idle for a minute, the various Chrome processes will sum up to between 800-1024MB of memory. You know how much Firefox with 8 tabs takes? 420MB.
Apparently people don't like this comment, but unlike some I do not possess scads and scads of RAM.
- zanny 13y agoThe underdog has room to improve - the reigning king has a throne to rest its laurels upon. I imagine Chrome will pick back up soon, Google needs to make a move on web apps in Android before the Firefox Marketplace steals the webapp momentum.
- quenlinlom 13y agoChrome has gone from the 'fastest' (whatever that means) and 'leanest' (ditto) to one that has the (penultimate) worst cold start times[1] and worst memory efficiency[2]. [1] http://www.tomshardware.com/reviews/chrome-27-firefox-21-opera-next,3534-4.html http://www.tomshardware.com/reviews/chrome-27-firefox-21-ope... [2] http://www.tomshardware.com/reviews/chrome-27-firefox-21-opera-next,3534-9.html http://www.tomshardware.com/reviews/chrome-27-firefox-21-ope...
- derefr 13y agoMy hypothesis is that Chrome is lately sacrificing memory for speed by doing heavier matryoshka caching on the rendered parts of a page. This is important for, say, smoothly compositing DOM elements on top of a WebGL canvas, or compositing CSS3-animated elements into a scrollable div. (Actually, I'd think this would cause higher video memory usage, not regular memory usage, but I'm not quite sure how Chrome tracks video memory; is it all grouped together as the memory usage of the "GPU process" in Chrome's task manager?)
- deleted 13y ago[deleted]