Firefox uses something called Multiprocess Firefox. This involves several content processes. In “multiprocess Firefox”, Firefox runs web content for all tabs separately from the main Firefox process for increased security and performance. Firefox claims that using multiple content processes can further increase performance and minimize the impact of content process crashes.
Content Process Limit Increasement From 4 to 8
Today, TechDows reported that Firefox has brought a change to the Content Process Limit. Up until Firefox 76, the maximum content processes that could be run at the same time was set to 4. However, TechDows claims that after successful testing by Firefox, they will be changing the limit from 4 to 8 in the upcoming version. This report was confirmed by a Memory advocate at Mozilla. The news was confirmed in a blog post. The blog post stated noted that doubling the content processes only brought about a 6% increase in memory.
It will be interesting to see how this change will affect different types of PC’s. How big of a change will it bring to PC’s with a small amount of memory? Firefox themselves have stated that “having too many content processes can slow down your computer, and consequently, Firefox”. Hopefully, Firefox has tested the feature under different circumstances and scenarios.
The new feature will be available in the upcoming Firefox 66 update. The feature is currently in beta mode. To download the beta version simply follow these steps:
- Click on hamburger menu >options > General >Performance
- Uncheck “Use Recommended Performance Settings”
- You can notice the “Content Process limit” as 8 (default).
As mentioned above, you don’t necessarily have to run 8 Content processes, you can lower this number to any number that suits you best below 8 and above 4. You can read more in TechDows article here. Mozilla is also trying to actively solve memory overhead problem in Firefox. They have already started tests on their tab unloading feature, which will appear in Firefox 67. You can read more about that here.