E10s/Status/Dec17: Difference between revisions

E10s/Status/Dec17 (view source)

Revision as of 22:23, 21 December 2015

791 bytes removed , 21 December 2015

→‎Why yellow? e10s is designated 'yellow' or 'at risk' because:

Vladan

Confirmed users

356

edits

@@ Line 23: / Line 23: @@
 *'''Validation for Stability and Performance: '''
-**'''Aurora 43.0 A/B Telemetry Experiment''' results are posted, [http://nbviewer.ipython.org/github/vitillo/e10s_analyses/blob/master/aurora/e10s_experiment.ipynb here]. {{bug|1193089}} Conclusions and action items based on findings are being triaged/discussed in a bi-weekly perf/e10s meeting. Perf plan is here, http://bit.ly/1XtGR4h. List of probes are here: http://bit.ly/1NeBIvM
+** Birunthan :poiru is going to post a summary of e10s vs non-e10s telemetry from the Aurora 43 experiment on the m.d.platform newsgroup this week. Draft here: https://docs.google.com/a/mozilla.com/document/d/1bRWybYcuTefO9qUPkul_r6rN-rl3QOAG_GpeJiYWhzs/edit?usp=sharing
-**'''Beta 43.0 A/B Telemetry Experiment''' was scheduled for 11/20. Plan for 7.5% of the population to have e10s enabled. We have decided to roll this out for 44.0 Beta 1 on Dec 16th instead of 43.0 Beta 7. Why? Because we don't have 100% parity for stability Meta bug = {{Bug|1222894}}.
+** '''Beta 44 A/B Telemetry Experiment''' is live: https://bsmedberg.github.io/telemetry-experiments-dashboard/
-** '''e10s performance measurement updates'''
+*** The experiment couldn't begin until last weekend because the first Beta 44 build was delayed
-*** Nov 26th triage: [https://docs.google.com/spreadsheets/d/1FIaGNv1q750mo9S7cJJY_8erbiF7j9snyX8Yd0diAbA/edit#gid=0 spreadsheet]
+*** This experiment is going to be run until January 11th (tentative end date)
-*** Top priority is confirming the apparent e10s responsiveness deficit {{bug|1182637}} & {{bug|1223780}}
+** Dec 12th e10s Telemetry probe triage: [https://docs.google.com/spreadsheets/d/1FIaGNv1q750mo9S7cJJY_8erbiF7j9snyX8Yd0diAbA/edit#gid=307269420 spreadsheet]
-**** {{bug|1224374}}: we need to expand BHR stack coverage to narrow down source of the difference in responsiveness
+** {{bug|1182637}}: the BHR/event-loop-lag responsiveness deficit in e10s has been confirmed first-hand with an extension that visualizes the BHR jank measurements: https://github.com/chutten/statuser
-**** {{bug|1228437}}: e10s child processes aren't reporting BHR, this means the measured responsiveness gap is worse than currently thought
+*** BHR reporting still needs to be improved to narrow down the origins: {{bug|1224374}}
-*** added probes for e10s memory usage {{bug|1198209}}, fixed probe for UI event lag {{bug|1198196}}, fixed AsyncShutdown dash {{bug|1222884}} & separated e10s vs non-e10s signatures {{bug|1222885}}
+** There is also a known regression in e10s page-load speed in Talos & Telemetry data
-*** adding probes for scrolling smoothness {{bug|1228147}} & session-restore time {{bug|1214158}}
-*** reviewing existing probes to confirm they are meaningful for e10s comparison: page load probes {{bug|1228020}}, content process crash probes {{bug|1227312}}, active usage hours {{bug|1187069}},
 ** Performance Tracker Meta {{Bug|1198187}}
-** Dashboard to depict areas of strength and where we need to improve is in progress: {{Bug|1210649}}. Next steps include identifying milestones for when this will be usable.
 *'''Add-Ons + WebExtensions:'''
@@ Line 52: / Line 48: @@
 ** We should be good to have our tests for windows enabled by Fx45/Fx46. mochitest-devtools on Windows 7 is about to be enabled {{bug|1221499}}. Server capacity is an issue we need to balance.
 ** All Linux tests are enabled (that are of priority).
 ==Release Schedule==
 Currently Proposed Schedule is to enable e10s by default for Users without Add-Ons for 45.0 and target a larger population for 46.0

E10s/Status/Dec17: Difference between revisions

E10s/Status/Dec17 (view source)

Revision as of 22:23, 21 December 2015

Navigation menu

Search