Confirm
1,982
edits
Changes
reformatting
=Overview = Goals ==
After e10s is enabled for all users, the next step is to introduce multiple content processes. The goal is to bring out the most from the multi process architecture we introduced with e10s, gain performance where it's possible and minimize the impact of content process crashes. The challenge is to achieve this without sacrificing the advantage we currently have in memory usage compared to our competitors.
One explicit non-goal of this project is to nest content processes for e.g. iframes. There is work underway to do that in {{bug|1277066}} in parallel to this project.
=Bug tracking = Roadmap = ==Triage == M1* [Nightly {{bug|1303113}}]https: enable 2 content processes on nightly (Done) //bugzilla.mozilla.org/buglist.cgi?list_id=13712205&resolution=---&status_whiteboard_type=anywordssubstr&query_format=advanced&status_whiteboard=Apart a few corner cases 2 content processes are fairly stable for everyday usage. Our hope is that by enabling 2 content processes on nightly despite a few known issues that will be time consuming to fix e10s-multi%3AM%3F%2C%20e10s-multi%3A%3F Triage list] (session storage / shared workers) we will get better bug reports early.* Ignore memory footprint.* Fix crash report in background tabs {{bug|1241459}}* '''Known issues that will block riding the train but will not block enabling 2 content processes on nightlye10s-multi:?'''** Service/Shared workers should run in their own process: {{bug|1231208}}** Some test will need some refactoring: {{bug|1301015}} but for now we will force them to use single content process: {{bug|1301340}}whiteboard)
==Priorities = M2=* [Aurora {{bug|1304546}}]https: Correctness, Measuring Performance and Memory, and Scaling to 4 Processes (Done)//bugzilla.mozilla.org/buglist.cgi?priority=P1&list_id=13712208&resolution=---&status_whiteboard_type=anywordssubstr&query_format=advanced&status_whiteboard=e10s-multi%3A%2B P1]* Measure the memory footprint of content processes[https://bugzilla.mozilla.org/buglist.cgi?priority=P2&list_id=13712208&resolution=---&status_whiteboard_type=anywordssubstr&query_format=advanced&status_whiteboard=e10s-multi%3A%2B P2]* Measure startup of content process ({{bug|1336389}}, {{bug|1304790}})* Start optimizing memory use* Prepare to go beyond 2 content processes (aiming for 4 initially {{bug|1336398}})[https://bugzilla.mozilla.org/buglist.* Service Workers in it's own content process <cgi?priority=P3&list_id=13712208&resolution=---&status_whiteboard_type=anywordssubstr&query_format=advanced&status_whiteboard= we are not going to block on a full implementation of this. * AWSY ({{bug|1272113}})e10s-multi%3A%2B P3]
=== M3[Beta {{bug|1304547}}]: Optimization and Preparing for Release ===* Memory optimization * Performance optimization* Solidifying Automated tests Initial Rollout (working with module ownerscompleted 8/1/2017)* General Convergence; focusing on quality=
==Release Criteria==
* '''Crash Rates''' need to be low enough that they have little, if any perceivable impact to the overall crash rates. See the crash rates starting with Firefox 54 Beta, [https://sql.telemetry.mozilla.org/queries/4355#8685 here].
* '''Performance''' metrics including memory-based metrics are in the [https://wiki.mozilla.org/Electrolysis/Multi_Release_Criteria release criteria wiki page]
* '''We may need to activate e10s-multi based on physical RAM size''' depending how the number of content processes impacts such memory. We have a hypothesis for both cases (increased number of content process will either benefit systems with lower RAM or make things worse).
==Release Plan==
* e10s-multi was enabled with 4 processes in Firefox 55 Nightly and currently beta experiments are being conducted in Firefox 54. Read more about the experiments, [https://wiki.mozilla.org/Electrolysis/Experiments#Beta_54 here].
* [https://bugzilla.mozilla.org/show_bug.cgi?id=1336380 Improve content process startup time]
* [https://docs.google.com/a/mozilla.com/document/d/14E5ERudaZrx-qcOLttXGkV6DgHIyp3h9IZoqnhuO7X8/edit Process Model] (2012)
* Recent [https://groups.google.com/forum/#!searchin/mozilla.dev.platform/e10s$20multiple$20processes/mozilla.dev.platform/NHIjpGvOelE/_A9IJWsP0fUJ dev.platform] discussion
== Meetings =Teams =We are meeting every week at 9am PDT (6pm CEST) starting on June 28.TBD
