E10s/Status/May5: Difference between revisions

From MozillaWiki
< E10s‎ | Status
Jump to navigation Jump to search
 
(6 intermediate revisions by the same user not shown)
Line 1: Line 1:
[[File:Yellow-sm.jpg|thumbnail|left]]<br>
[[File:Yellow-sm.jpg|thumbnail|left]]<br>


=e10s Update: '''May 5'''=
=E10s Update: '''May 5'''=
==Executive Summary==
==Executive Summary==
* The biggest news this week is that all Release Criteria that has been signed off continues to pass in Firefox 47 Beta. There are no new regressions thus far. This is according to our latest [ https://github.com/vitillo/e10s_analyses/blob/master/beta47-ex1/e10s_experiment.ipynb derived data set] which ran from April 27-May 4. We will run these data sets weekly in order to evaluate performance on an ongoing basis.
* As of Firefox Release 53 (Early May) [https://sql.telemetry.mozilla.org/queries/972#1659 54.77% of the total release population have e10s] (as compared to 52.82 in Firefox 42 in early April). Single process e10s is active for non add-on users, and add-on that are web extensions or SDK add-ons actively marked compatible by the author.  


* Our #1 risk remains stability. Our [https://sql.telemetry.mozilla.org/queries/271#445 crash rates for beta 1] are still higher (27.2) vs. non-e10s (9.2). A full 33% of e10s content crashes in b1 were caused by {{bug|1255823}} which is fixed for b2, so we expect the crash rate for b2 to stabilize around 20. Getting to 20 or below is our stated goal for next week.
* e10s-multi was enabled as of Firefox 54 Nightly with 4 content processes. As of Firefox 54 Beta 1, we launched our first multi A/B test with an experiment split of 10% Control and 90% test. As of Beta 3, the Test population is split evenly across  two cohorts: [https://bugzilla.mozilla.org/show_bug.cgi?id=1349363 single process and multi-process]. The metrics we are monitoring since we released the first experiment include:
** [https://sql.telemetry.mozilla.org/queries/4386/source#8758 E10s-Multi Population]
With the approach of Firefox 47 Beta 4 on May 10, stability and unearthing [https://docs.google.com/document/d/150XUlvXi13mliWIixS5x5DoLE14ySxItBhQfCIKg1NI/edit important details we need to line up for a staged rollout to GA] remains our central focus.
** [https://sql.telemetry.mozilla.org/queries/4355#8687 Stability Metrics]
** [https://wiki.mozilla.org/Electrolysis/Multi_Release_Criteria Performance Release Criteria]
* Our forecast for the engineering schedule tracks to being MVP as of 55 and we are working to uplift as much as possible to 54 with an eye towards shipping in 54 so long as we meet or exceed our release criteria (we are aiming for release 54 for initial roll-out, for at least some part of the population).


==Why yellow? e10s is designated 'yellow' or 'at risk' because: ==
=={{mok}} E10s-Multi==
Stability is our #1 risk to our plan to stay enable for the entire beta cycle in Firefox 47. We also need to continue to make progress on an issue with [https://bugzilla.mozilla.org/show_bug.cgi?id=1260769 slow scripts]. All other areas of release criteria are looking good.
* The team is currently focused on correctness, measuring performance and memory, and Scaling to 4 Processes. You can read more about what this means in the  [https://wiki.mozilla.org/Electrolysis/Multiple_content_processes e10s-multi wiki]. Basically, we are working hard so multi can ride the trains for 54/55.
*The E10s-Multi plan is taking shape: our current forecast predicts that [https://docs.google.com/a/mozilla.com/spreadsheets/d/1ECXZZatvbYx9uLV5zo7TzlkaTBJUcEnp2dHdFn8-pQs/edit?usp=sharing engineering MVP] will be complete before the end of Firefox 55. We are currently 80% complete.
** Our last hard Service Workers dependency {{bug|1346247}} was just uplifted to Aurora 55 as of this morning. \o/ 
** Beta experiment design has been determined and we are making progress with the system add-on changes and subsequent validation {{bug|1349363}}, {{bug|1352388}}.
** Creating a detailed week-by-week [https://docs.google.com/spreadsheets/d/1ECXZZatvbYx9uLV5zo7TzlkaTBJUcEnp2dHdFn8-pQs/edit#gid=302917609 release plan is a work in progress].
** Final approval on [https://wiki.mozilla.org/Electrolysis/Multi_Release_Criteria release criteria] and making sure any new telemetry requirements are filed.
** Creating a test plan is assigned and currently in progress.


==Next Steps==
=={{mok}} RTL Support, Touchscreen Support, A11y ==
* 04/10: Firefox 47 Beta 3 Ships
* E10s support for RTL versions of [https://bugzilla.mozilla.org/show_bug.cgi?id=1033483 Firefox on Linux] is still planned for Firefox 52 (Windows and Mac shipped in Firefox 50).
* 05/11: Second derived data set available (2 weeks of data)
* A11y and touchscreen support has landed in 51. Support Windows 8 and Windows 10 shipped in 52.  
* 05/12: Quality check point
* The plan is to ship A11y for Windows for Firefox 55.
 
==Release Criteria==
* See the wiki for up-to-date [https://wiki.mozilla.org/Electrolysis/Release_Criteria e10s release criteria status]
 
==Add-Ons + WebExtensions==
* Decision to not have an allow list has been made, we will take a more efficient approach. Only add-ons that have self identified as e10s compliant can be part of the e10s activation audience at first -in addition to all add-ons that are webextensions. See {{bug|1249060}} for more details.
* General roll-out plan for including extensions is [https://docs.google.com/spreadsheets/d/1OFYrrvAFg8y1mZOEbuIR1axxtV8eul_be6ad9fe8JB0/edit?usp=sharing here].
 
==Automated tests==
* Everything we can have enabled in production is enabled, everything else is enabled on a separate branch called 'Ash'.
* We have all tests be owned
* We would like each directory signed-off by test owners week of 04/25
*We're tracking all the tests and who owns them, [https://docs.google.com/spreadsheets/d/10UeyRoiWV2HjkWwAU51HXyXAV7YLi4BjDm55mr5Xv6c/edit#gid=1777180571 here]
*We are tracking tests that are running and passing on some platforms, but are disabled on others.From a feature coverage point of view, it's in pretty great shape. There's very little that is disabled both on opt *and* debug on a same platform (meaning that that test is not running on this platform). Look for the "Fully disabled in a platform" entries in this [https://docs.google.com/spreadsheets/d/1oBnRct8FuTnAoVfbE08m10UHi1_5kOFaOPglJ6ittWc/edit#gid=0 spreadsheet].
 
==A11y==
* Proposed technical path to encourage a11y clients to communicate directly with the content process {{bug|1258839}}. dbolter is getting some first impressions from clients to see if this is a viable approach.
* We're also looking into Windows touchscreen/a11y compat, see more information as the plan is taking shape, [https://public.etherpad-mozilla.org/p/a11y+e10s here].
 
==Milestones==
We are at the point where we are setting milestones weekly; given the complexity of deliverables, we are using a [https://docs.google.com/a/mozilla.com/spreadsheets/d/101ra3HjqyufjP79JkGa4e0RyHPLVlJXS43rXtKuoJw4/edit?usp=sharing Trackback Schedule] to keep everything organized.
 
==Release Schedule==
{| class="wikitable"
|-
! Date !! Trunk !! Aurora !! Beta !! Release
|-
| 3-07 || 48 default || 47 default || 46 A/B Tests|| 45 off
|-
| 4-18 || 49 default || 48 default || 47 A/B Tests, Possible Rollout (add-ons = ally = no) || 46 off
|-
|6-07 || 50 default|| 49 default || 48 Possible Rollout (add-ons + ally = no)  || 47 off
|-
|8-02 || 51 default || 50 default || 49 Possible Rollout (add-ons + ally = no) || 48 Possible Rollout (add-ons + ally = no)
|-
|9-13 || 52 default || 51 default || 50 Possible Rollout (add-ons + ally = no) || 49 Possible Rollout (add-ons + ally = no)
|}

Latest revision as of 01:18, 6 May 2017

Yellow-sm.jpg


E10s Update: May 5

Executive Summary

  • As of Firefox Release 53 (Early May) 54.77% of the total release population have e10s (as compared to 52.82 in Firefox 42 in early April). Single process e10s is active for non add-on users, and add-on that are web extensions or SDK add-ons actively marked compatible by the author.
  • e10s-multi was enabled as of Firefox 54 Nightly with 4 content processes. As of Firefox 54 Beta 1, we launched our first multi A/B test with an experiment split of 10% Control and 90% test. As of Beta 3, the Test population is split evenly across two cohorts: single process and multi-process. The metrics we are monitoring since we released the first experiment include:
  • Our forecast for the engineering schedule tracks to being MVP as of 55 and we are working to uplift as much as possible to 54 with an eye towards shipping in 54 so long as we meet or exceed our release criteria (we are aiming for release 54 for initial roll-out, for at least some part of the population).

[ON TRACK] E10s-Multi

  • The team is currently focused on correctness, measuring performance and memory, and Scaling to 4 Processes. You can read more about what this means in the e10s-multi wiki. Basically, we are working hard so multi can ride the trains for 54/55.
  • The E10s-Multi plan is taking shape: our current forecast predicts that engineering MVP will be complete before the end of Firefox 55. We are currently 80% complete.
    • Our last hard Service Workers dependency bug 1346247 was just uplifted to Aurora 55 as of this morning. \o/
    • Beta experiment design has been determined and we are making progress with the system add-on changes and subsequent validation bug 1349363, bug 1352388.
    • Creating a detailed week-by-week release plan is a work in progress.
    • Final approval on release criteria and making sure any new telemetry requirements are filed.
    • Creating a test plan is assigned and currently in progress.

[ON TRACK] RTL Support, Touchscreen Support, A11y

  • E10s support for RTL versions of Firefox on Linux is still planned for Firefox 52 (Windows and Mac shipped in Firefox 50).
  • A11y and touchscreen support has landed in 51. Support Windows 8 and Windows 10 shipped in 52.
  • The plan is to ship A11y for Windows for Firefox 55.
Retrieved from "https://dev.wikimo.nonprod.webservices.mozgcp.net/index.php?title=E10s/Status/May5&oldid=1170526"