canmove, Confirmed users, Bureaucrats and Sysops emeriti
5,401
edits
E10s/Status/May26: Difference between revisions
→e10s-Multi Release Criteria
| 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 as a result of our analysis {{bug|1347984}} has landed in beta and one fix will ship in 55. but it turns out it is not reproducible. | ||
*{{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. | ||