3 ms·
TBH, I used to hate Firefox's performance, because even loading Facebook froze the entire browser for several msecs (enough to be perceptible), but recently I t
by Aldo_MX 11y ago
TBH, I used to hate Firefox's performance, because even loading Facebook froze the entire browser for several msecs (enough to be perceptible), but recently I turned e10s[1] on and the browser feels almost as responsive as Chrome now.
The documentation seems to be outdated, there seems to be an A/B testing right now, and it's recommended to turn off some extensions[2], but this is how I forced e10s to be turned on in `about:config` in the beta:
{
e10s.rollout.cohort: "control",
e10s.rollout.cohortSample: 78,
extensions.e10sBlockedByAddons: false
}
[1] https://wiki.mozilla.org/Electrolysis https://wiki.mozilla.org/Electrolysis
[2] https://www.arewee10syet.com/ https://www.arewee10syet.com/
- the8472 11y agoThat applies if you're on beta. Dev Edition and Nightly get e10s by default
- felipc 11y agoThanks for testing e10s! There's a simpler a better way to test it though, which is just setting `browser.tabs.remote.autostart` to true. These prefs that you mentioned won't stick (they will be reset after startup) and are just used for some internal state. I'll make sure the info on that wiki page is up to date for people who want to test it. Note: Multiprocess is not available in the Release channel yet. Please use our Developer/Test channels if you want to use it. Also, if you have add-ons, multiprocess is by default blocked from running on Beta (but allowed on Nightly/Aurora). If you're on Beta and want to use it together with add-ons, look at that wiki page to see how to work around that. Or just use Aurora :)
- Aldo_MX 11y agoThank you and every person involved for e10s! :)