3 ms·
Well, here is one thing I observed. Chrome allocates different process for every tab. Firefox doesn't do that. Just one process for all tab. Suppose I open 10
by godelmachine 9y ago
Well, here is one thing I observed.
Chrome allocates different process for every tab. Firefox doesn't do that. Just one process for all tab.
Suppose I open 10 tabs each on Chrome & Firefox. And suppose every tab needs 100MB of memory.
If you look up in task manager -
Chrome - 10 tabs - 10 different process - 100MB each = 1000MB = roughly 1GB
Firefox - 10 tabs - only 1 process - 1000MB = roughly 1GB for that one process.
- sebazzz 9y agoSounds like your Firefox version is out of date. Multi process Firefox has landed quite a while ago, with different memory and performance characteristics.
- godelmachine 9y agoI'll check. Guess Firefox copied this feature from Chrome.
- littlestymaar 9y agoFortunately they didn't : they use one process for the browser UI, and a few (like two or four) processes for tabs which are dispatched between those process. It's way better than Chrome in term of memory consumption when you have lots of tabs opened.
- Sylos 9y agoI think, the number of processes (by default) is set to how many cores you have on your CPU. That way you can achieve almost the maximum of parallelism with a minimum of RAM use.
- zamber 9y agoYou don't have to guess - https://wiki.mozilla.org/Quantum https://wiki.mozilla.org/Quantum
- zamber 9y agoCurrently I have ~90 tabs open in Firefox. It uses 3.3GB of RAM and 1-3% of CPU (on a i7 though). Closing and reopening is faster than doing the same in Chrome with far less tabs open. IMO it's they usual software cycle of bloat -> optimization -> new features -> bloat -> optimization...