- Apr 12, 2001
Mozilla yesterday announced the release of Firefox 54 web browser with new multi-process architecture that promises to make browsing with multiple tabs open faster and more stable, especially on computers with 8GB of memory or less.
With the latest release, Firefox uses up to four processes to run web page content across all open tabs. This means that a heavy, complex web page in one tab has a much lower impact on the responsiveness and speed of other tabs, according to Mozilla:
The old Firefox used a single process to run all the tabs in a browser. Modern browsers split the load into several independent processes. We named our project to split Firefox into multiple processes 'Electrolysis' (or E10s) after the chemical process that divides water into its core elements. E10s is the largest change to Firefox code in our history. Besides running faster and crashing less, E10S makes websites feel more smooth. Even busy pages, like Facebook newsfeeds, spool out smoothly and cleanly.
In Mozilla's own tests comparing memory usage for various browsers, it claimed that Firefox used significantly less RAM in macOS than both Safari and Chrome. The group has published an article on Medium explaining how the new E10s architecture works.
In one section titled "Why Chrome gets too hot when Firefox does not", Mozilla writes that Chrome's method of creating separate processes for each open tab can end up with each one consuming hundreds of megabytes of RAM, whereas Firefox reuses processes and content engines to limit memory usage.
Mozilla claims that Firefox's considerate memory usage means users with 8GB of memory or less can browse the web without the browser hogging resources, allowing them to do other things on their computer. Meanwhile, users with more than 8GB of RAM can bump up the number of content processes that Firefox uses to make it even faster.By default, Firefox now creates up to 4 separate processes for web page content. So, your first 4 tabs each use those 4 processes, and additional tabs run using threads within those processes. Multiple tabs within a process share the browser engine that already exists in memory, instead of each creating their own.
Users can test out the claims by downloading Firefox 54 for free from the Mozilla website.To change the number of content processes Firefox uses, enter about:config in your address bar, and adjust the number for the dom.ipc.processCount setting (we'll be exposing a visible preference for this in an upcoming release).
Article Link: Firefox 54 Promises Faster Browsing on Macs With Limited RAM