3 ms·

Part of the problem is that e10s Firefox by default still uses just one UI process and one "content" process, shared by all tabs. So a web page can't cause the

Part of the problem is that e10s Firefox by default still uses just one UI process and one "content" process, shared by all tabs. So a web page can't cause the UI to hang, but it can cause all other web pages to hang. Curious testers can go to about:config and set "dom.ipc.processCount" higher than 1 to increase the number of content processes. I suggest trying this only in Firefox Developer Edition or Nightly, and not in your main browsing profile, since there are still some serious bugs and active development related to this configuration (so consider it a chance to test future improvements, rather than something that’s ready for regular use): http://bugzil.la/e10s-multi http://bugzil.la/e10s-multi

Scarbutt 11y ago
When e10 becomes the default, will the number of content processes still default to 1?
- swinglock 11y ago
  Yes, the conclusion of the link says so.
  - Excavator 11y ago
    Where? I don't see any such conclusion. Mind quoting the relevant bit?
    - Ded7xSEoPKYNsDd 11y ago
      > Overall we see a 10-20% increase in memory usage for the 1 content process case (which is what we plan on shipping initially).
- Excavator 11y ago
  There's a bug open for basing it on the amount of cores and memory. https://bugzilla.mozilla.org/show_bug.cgi?id=1066789 https://bugzilla.mozilla.org/show_bug.cgi?id=1066789
- nnethercote 11y ago
  It'll be 1 at first. It's likely to then gradually be increased over time, probably to 2, then 4, maybe 8. Not sure about beyond that. I'm currently working on reducing memory usage to help with this, because that's the main downside of increasing the content process count. There are all sorts of trade-offs here: performance, memory usage, address space usage, security, crash-resilience, and they all tug in different directions.
winter_blue 11y ago
Wow, thanks! I use Firefox Developer Edition, and haven't seen any discernible improvement in performance with e10s, but setting "dom.ipc.processCount" higher than 1 already seems to be making my browser run faster.

Scarbutt 11y ago

When e10 becomes the default, will the number of content processes still default to 1?

swinglock 11y ago
Yes, the conclusion of the link says so.
- Excavator 11y ago
  Where? I don't see any such conclusion. Mind quoting the relevant bit?
  - Ded7xSEoPKYNsDd 11y ago
    > Overall we see a 10-20% increase in memory usage for the 1 content process case (which is what we plan on shipping initially).
Excavator 11y ago
There's a bug open for basing it on the amount of cores and memory. https://bugzilla.mozilla.org/show_bug.cgi?id=1066789 https://bugzilla.mozilla.org/show_bug.cgi?id=1066789
nnethercote 11y ago
It'll be 1 at first. It's likely to then gradually be increased over time, probably to 2, then 4, maybe 8. Not sure about beyond that. I'm currently working on reducing memory usage to help with this, because that's the main downside of increasing the content process count. There are all sorts of trade-offs here: performance, memory usage, address space usage, security, crash-resilience, and they all tug in different directions.

winter_blue 11y ago

Wow, thanks! I use Firefox Developer Edition, and haven't seen any discernible improvement in performance with e10s, but setting "dom.ipc.processCount" higher than 1 already seems to be making my browser run faster.