3 ms·
>No processes From my understanding, the initial rollout of multi-process has a single render process (in addition to the main browser process). There are ong
by sf_rob 10y ago
>No processes
From my understanding, the initial rollout of multi-process has a single render process (in addition to the main browser process). There are ongoing experiments to determine the optimal number of processes, so it's likely to increase soon. In the future you can force this to 1 by using the "dom.ipc.processCount" pref if you don't want your process manager to resemble Chrome.
- cpeterso 10y agoThat's correct. Firefox currently uses one main browser process, one content process (for all tabs), and a plugin sandbox process. Multiple content processes (aka "e10s-multi") are coming soon, currently two content processes are the default in Firefox Developer Edition (53) and Nightly (54). More content processes will be added, though the Firefox team is quite aware of the concerns about memory usage. The next step will probably be four content processes plus a ServiceWorker process. https://wiki.mozilla.org/Electrolysis/Multiple_content_processes https://wiki.mozilla.org/Electrolysis/Multiple_content_proce...
- yellowapple 10y agoI feel like that defeats the point of multiprocess; on Chrome at least, the one-process-per-tab model is intended to isolate tabs from one another without having to duplicate a bunch of work that the OS does already.
- sf_rob 10y agoYou're correct that it defeats one of the points of multiprocess, but you still get parallel performance gains trivially that will scale well as more cores are added as well as isolation of crashes where it doesn't kill your whole session.