Firefox has improved its multi-process architecture in order to isolate more content while keeping memory use low:
Firefox 54 launched with a more advanced multi-process architecture than the one we saw implemented in Firefox 48 last year. The improved architecture raises the number of processes enabled by default from two to five, which Mozilla argues is a "just right" compromise between low memory usage on one side and performance and security on the other.
[...] Switching to a simpler extension model allows Firefox to enable multiple processes and also isolate them in sandboxes. Mozilla previously enabled only two processes, one for the UI and one for content, last year, in Firefox 48. This ensured that the browser wouldn't hang as much due to web pages affecting the performance of the browser interface. It also brought partial sandboxing by keeping the content isolated from the browser (as much as possible).
Mozilla is now taking it to the next level by implementing one process for the browser interface and four for content. Why four? The organization believes that this is the "just right" amount of processes to have for the majority of users, and also in terms of optimizing memory usage.
[...] Mozilla ran its own memory usage benchmarks, which showed significant memory usage reduction compared to Chrome:
- Windows 10 — Chrome used 1.77X memory as Firefox (64-bit), and 2.44X as Firefox (32-bit)
- macOS — Chrome used 1.36X memory as Firefox (64-bit)
- Linux — Chrome used 1.42X memory as Firefox (64-bit)
(Score: 0) by Anonymous Coward on Thursday June 15 2017, @03:40PM
nice. I got an old server instead of buying ECC RAM too.