118
edits
Changes
Fix some English wording and add timelines to milestones
== 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 scarifying our sacrificing the advantage we currently have in memory usage compared to our competitionscompetitors.
== What to expect ==
First , we want to will enable 2 content processes then after some optimization increase that and fix correctness bugs in the DOM and frontend components. Then we will start ramping up the number of content processes while optimizing memory use in order to a reasonable capavoid using too much memory overall. Once we have that we can think about advanced process models, sandboxing and how can we get the most out of multiple content processes.
== Roadmap ==
=== M1: general correctness (1-2 months) ===
* Fix correctness bugs (making 2 processes correct).
* Ignore memory footprint.
* Service/Shared workers in their own process.
=== M2: preparation for scaling (3 months) ===
* Measure the memory footprint of content processes.
* Start optimizing memory use.
* Strategy to go beyond 2 content processes (aiming for 5 initially).
=== M3: scaling (ongoing) ===
* Currently vaguely defined, but the main focus will be memory optimization and the goal is to enable more content processes.
