E10S Multi UI Preferences As a user curious about the new Electrolysis multi-process feature, I would like to know more about how Firefox is configured for my system as well as potentially be able to adjust the e10s multi settings in about:prefs. * As a user on a system with less than 4GB of RAM, I am curious to know how much RAM Firefox is actually using. * I would like to know how much RAM is being used by Firefox as well as by web content and addons * I would like to be able to access RAM usage of web pages per page * If I see that Firefox is using too much RAM by default, I would like to be able to change the setting to use as little RAM as possible. * As a Photoshop user I would like to minimize the ram usage of all other applications, including Firefox * As a user on a system with less than 2GB of RAM, I would like to limit Firefox to the least RAM usage possible. * As a user on a workstation that has 32GB of RAM and > 4 cores / > 2 cpus, I would like to use as much RAM as possible in order to improve performance and responsiveness. * As a user who is curious about Firefox’s support for multiple processes, I would like check that Firefox has chosen a multiprocess configuration that is appropriate for my system.
We'd like to explore how to expose multi-process configuration options to end-users.
Hey Phillip - what's the status of this? Last I heard I had the impression that TDC was going to fold the work into the other prefs stuff, but given that multi may ship in 54 we may want to ship something very simple as a companion feature.
Yes, TDC is working on it (NI Tina). They are about to do some user testing right now, but I am not fully in the loop here. We should look at how far it has gotten. I think the basic concept we looked at when I was in Toronto is still a candidate, but I assume that there's something better by now :)  https://mozilla.invisionapp.com/share/BWADX1YR4#/217291974_Artboard_1
We have some ongoing implementations for the reorganization of about:prefs, so we try to help performance options to find a right category in the new organization by conducting a user test. I hope that we can ship the test this week so that we can have the result as soon as possible. As far as I know, about:prefs currently is short of dev resources so it's hard to have new changes. For the schedule of about:prefs, I think Cindy can share more details about it :)
We've been using student resources (from Michigan State U) and can keep them till the end of April. We have a status check meeting with them tomorrow and should have a better idea on the progress. We need to scope in the part that's needed for Photon release or else there will be no resources after April.
Got @fischer to work on this. Targeting 55.
(In reply to chsiang from comment #5) > Got @fischer to work on this. Targeting 55.
Hum, I thought Evan is going to help us out with mentorship from Fischer, given that he is wrapping up storage mgmt? Anyway, I will have the sort this out.
It's your call Tim!
hi all, per discussion with Evan, now we have following 2 dependencies: 1. find out if page fetching API exists? Evan is on this one. 2. Come out final UX spec including review by USA side. Tina is on this one, she will keep us posted. once these 2 above were clarified, an ETA date for fixing this bug can be defined with accuracy. for now, we are still targeting to fix it by 2nd nightly 55. hope this answers some of your questions. thank you very much
(In reply to Francis Lee [:frlee] from comment #9) > hi all, > > per discussion with Evan, now we have following 2 dependencies: > 1. find out if page fetching API exists? Evan is on this one. Found, looks like `network.prefetch-next` is what we want. Thanks for Henry's help. > Link prefetching is a browser mechanism, which utilizes browser idle time to download or prefetch documents that the user might visit in the near future.  : https://developer.mozilla.org/en-US/docs/Web/HTTP/Link_prefetching_FAQ
> 2. Come out final UX spec including review by USA side. Tina is on this one, > she will keep us posted. Just a reminder for us. We will also send our UX spec to Preference code module owners or reviewers (Jared and Gijs) and get the feedback from them.
The prefs to control process count is dom.ipc.processCount.* . The types definition is at .  http://searchfox.org/mozilla-central/rev/fcd9f1480d65f1a5df2acda97eb07a7e133f6ed4/modules/libpref/init/all.js#3082  http://searchfox.org/mozilla-central/rev/fcd9f1480d65f1a5df2acda97eb07a7e133f6ed4/dom/ipc/ContentParent.h#40
I filed a meta bug (Bug 1354473) for our Performance settings section. We could discuss the UX spec for all performance settings we would like to add into Preferences and engineering items of other performance settings (except e10s multiprocess configuration) there.
This bug represents UX while other bugs under bug 1354473 (or bug 1354473 itself) represents engineering.
Is the spec considered complete? Let's close this one out if it does. (maybe link to it here or upload a final PDF for record keeping purpose, thanks)
Hey Tim, I'm OK with closing it :) You'll see the spec in Bug 1354473.
close it as comment 16.