From MozillaWiki
< E10s‎ | Status
Jump to: navigation, search

e10s Update: May 16

Executive Summary

  • e10s-multi was enabled as of Firefox 54 Beta 1 with 4 content processes. Currently 26.2% of the 54 Beta population has e10s-Multi enabled as compared to 21.15% last week. We are at a place in the project where we really don't have anything preventing the roll-out for Firefox 54 Release but we feel that we need to maintain an 'At Risk' profile until we have more time out in Beta. Though we have a great first pass at initial an telemetry performance data set, our sample sizes for Linux and Mac are low compared with Windows.We will remain yellow until we have more confidence we are meeting our release criteria at scale. Scroll below, to see more details.
  • The plan is to continue convergence in time to ship A11y for Windows for Firefox 55; this project is designated at risk due to the challenges with instability. A go/no-go will need to happen no later than June 3rd.

e10s-Multi Release Criteria

  • [ON TRACK] Stability. We have a tight correlation between single process and multi-process crashes which is good. We are concerned that the WebExtensions crashes in the content crash rate is higher than Non Web-Extensions. We thought we had a root cause with bug 1347984 but it turns out it is not reproducible. Ben Miroglio has an action item to dissect the WebExtensions crashes so we can (a) detect which WebExtensions are crashier and (b) detect which crashes are most frequent. Otherwise, our stability criteria is being met but Multi so far.
  • [ON TRACK] % of population shows us we'd like to increase the number of people we roll e10s-mutli out to in Beta 54 and this particular area was highlighted as 'At Risk' last week but can be considered 'On Track' as of this weeek. We have rolled out the beta Experiment to MPC=True Add-Ons to help increase our test population bug 1362493. One known risk item for MPC + Multi is the Lazy Tabs feature for Add-Ons isn't mutli compatible and we are working to see if it can be delayed bug 1363240.
  • [AT RISK] Performance numbers on Talos shows us a regression in responsiveness for TP05 which is being addressed.
  • [ON TRACK] Performance Telemetry shows us that there is parity between 4 processes and single process e10s so far. This is considered to be meeting our release criteria thus far, though as mentioned above, we would like the sample size for Mac OS and Linux to increase a bit. A few areas we are keeping our eyes on include:
  • [ON TRACK] Memory Usage is considered to be on track. Our criteria is to be better than Chrome and Eric's latest findings show us that we are. Gabor is adding telemetry so it is easy for us to see how many content processes are running when memory is being measured. When that lands, we will uplift to beta.

Upcoming Decisions and Milestones

  • May 23 Compare MPC=data to our current Performance and Stability baseline
  • A go/no-go decision for doing an initial roll-out for Multi in Firefox 54 will happen no later than June 3rd.
  • [DONE] The % of Beta Users with e10s-Multi activated in shows us that our initial experiment design doesn't activate E10s-Multi for as many users as we would like. 10% of the population is in the control group and 90% is in test, however, only 46% have e10s active and 21% which is has Multi enabled. We are currently activating e10s-Multi for users who either do not have add-ons installed or who are using WebExtensions only. Product's sentiment is that this approach is too conservative and is evaluating risk vs. reward for expanding the experiment to include MPC=True Add-Ons for e10s Multi. This decision will be made by May 12th.
  • [DONE] We should have complete data for our release criteria by EOD May 10

Engineering Status + Schedule

  • Engineering highlights include recently landed bug 1341008 Use the preallocated process manager by default which Preloads a content process in the background when the browser is idle and using that the next time we need one which will greatly improve load time.
  • Top issues we are investigating include:
  • bug 1363240 Content process limit specified by dom.ipc.processCount is not respected in some circumstances