Closed Bug 1213413 Opened 5 years ago Closed 4 years ago
Firefox needs multiple e10s content processes to isolate badly performing tabs (process-per-tab)
A tab’s performance should not depend on the behavior of other unrelated tabs. We need process-per-tab E10S to isolate tabs' performance from each other. Obviously the solution is not as simple as spawning a process for each tab. There needs to be a limit to the number of content-processes, there need to be rules for sharing content processes among tabs when the limit is reached, and the memory overhead of each content-process needs to be trimmed. As an example of the potential impact of background tab activity, we measured the impact of loading GMail in a background tab while scrolling a page in a foreground tab. Our results: https://docs.google.com/spreadsheets/d/13SgzLq6IWj38LvhPnU7YE07F0XsZaYSNyPBBMZch5_M/edit#gid=0 * In the tests above, the foreground tab was alternately Yahoo search results, a Twitter user page, and a Facebook profile * The test laptop was a reference content-perf laptop: HP 14t i3-5010u in the stock “HP Recommended” (balanced) power profile, plugged into power
Status: NEW → RESOLVED
Closed: 4 years ago
Resolution: --- → DUPLICATE
Duplicate of bug: e10s-multi
You need to log in before you can comment on or make changes to this bug.