canmove, Confirmed users, Bureaucrats and Sysops emeriti
5,401
edits
E10s/Status/May26: Difference between revisions
→Engineering Status + Schedule
| (4 intermediate revisions by the same user not shown) | |||
| Line 12: | Line 12: | ||
==e10s-Multi Release Criteria== | ==e10s-Multi Release Criteria== | ||
*{{mok}} [https://sql.telemetry.mozilla.org/queries/4355#8687 Stability]. We have a tight correlation between single process and multi-process crashes which is good. We decided that th WebExtensions crashes in the content crash rate is being higher than Non Web-Extensions was enough risk to not include WE extensions users in this initial roll-out for Firefox 54. | *{{mok}} [https://sql.telemetry.mozilla.org/queries/4355#8687 Stability]. We have a tight correlation between single process and multi-process crashes which is good. We decided that th WebExtensions crashes in the content crash rate is being higher than Non Web-Extensions was enough risk to not include WE extensions users in this initial roll-out for Firefox 54. There are a couple of fixes happening: a fix for initial signature which started this conversation {{bug|1347984}} has landed in beta and fixes found in {{bug|1358879}} will also help and shall ship in 55. | ||
*{{mok}} [https://sql.telemetry.mozilla.org/queries/4400/source#8797 % 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 week. 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 e0s mutli compatible and we are working to see if it can be delayed {{bug|1363240}}. | |||
*{{mok}} [https://metrics.mozilla.com/protected/bmiroglio/multi/e10sMulti_experiment.html 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: | *{{mok}} [https://metrics.mozilla.com/protected/bmiroglio/multi/e10sMulti_experiment.html 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: | ||
* | |||
*{{mok}} FX_TAB_SWITCH_SPINNER_VISIBLE_MS which has regressed slightly with multi, {{bug|1341008}} and {{bug|1342927}} are considered mitigations that have landed in Firefox 55. We don't think what we see in 54 is enough to block roll-out at this point. | |||
** For tab switching metrics, it's worth noting that only about [https://mzl.la/2rmQhpD 3/4 of the beta population are using 3 or fewer tabs so we might find we have different results on release]. | ** For tab switching metrics, it's worth noting that only about [https://mzl.la/2rmQhpD 3/4 of the beta population are using 3 or fewer tabs so we might find we have different results on release]. | ||
*{{mok}} [https://wiki.mozilla.org/Electrolysis/Multi_Release_Criteria#Are_We_Slim_Yet_.28AWSY.29 Memory Usage] is considered to be on track. Our criteria is to be better than Chrome and [http://www.erahm.org/2017/05/15/firefox-memory-usage-with-multiple-content-processes/ 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. | *{{mok}} [https://wiki.mozilla.org/Electrolysis/Multi_Release_Criteria#Are_We_Slim_Yet_.28AWSY.29 Memory Usage] is considered to be on track. Our criteria is to be better than Chrome and [http://www.erahm.org/2017/05/15/firefox-memory-usage-with-multiple-content-processes/ 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== | ==Upcoming Decisions and Milestones== | ||
* | * [DONE] A go/no-go decision for doing an initial roll-out for Multi in Firefox 54 will happen no later than June 3rd. | ||
* [DONE] May 23 Compare MPC=data to our current Performance and Stability baseline | |||
* [DONE] [https://sql.telemetry.mozilla.org/queries/4400/source#8797 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 [https://wiki.mozilla.org/Firefox/AddOns/Status/current#Multiplecontent_Processes 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] [https://sql.telemetry.mozilla.org/queries/4400/source#8797 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 [https://wiki.mozilla.org/Firefox/AddOns/Status/current#Multiplecontent_Processes 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 | * [DONE] We should have complete data for our release criteria by EOD May 10 | ||
==Engineering Status + Schedule== | ==Engineering Status + Schedule== | ||
* Engineering highlights include | * Engineering highlights include combing through the back log and preparing for planning. Patch volume is down because of the palce we are in the project; we are finished with convergence and keeping an eye on incoming issues. We are currently working to land {{bug|1364849}}. Next up, we will be planning for the future which will happen during the San Francisco work week. | ||