E10s/Status/Jan15: Difference between revisions

Line 18: Line 18:
==Validation for Stability and Performance==
==Validation for Stability and Performance==
*'''Beta 44 A/B Telemetry Experiment''' ended on Jan 3. We found that the population included in the experiment included users with Add-Ons and people with a11y enabled. Both of which we originally intended to be omitted from the experiment.  
*'''Beta 44 A/B Telemetry Experiment''' ended on Jan 3. We found that the population included in the experiment included users with Add-Ons and people with a11y enabled. Both of which we originally intended to be omitted from the experiment.  
** We need the BHR responsiveness measurement from the e10s content process in order to accurately compare e10s with non-e10s. {{Bug|1228437}}.
** We need the BHR responsiveness measurement from the e10s content process in order to accurately compare e10s with non-e10s. {{Bug|1228437}}. Currently, we are not accurately measuring responsiveness.  
**
**We also have recently uplifted a patch to fix the fact that we're over counting crash reports for the content process {{Bug|1227312}}.
**At this point, we are working on the design for the Beta 45 experiment and being certain to curate the aforementioned uplifts (long with with others) that fix telemetry measures before we deploy to 45.
** Telemetry E10S Measurement Meta {{Bug|1222849}}
** Performance Tracker Meta {{Bug|1198187}}


*'''Beta 45 A/B Telemetry Experiment''' goal is to deploy as of Firefox 45 Beta 1 on January 27th
*'''Beta 45 A/B Telemetry Experiment''' goal is to deploy as of Firefox 45 Beta 1 on January 27th
Line 29: Line 32:
**''Feb 5'': Run existing data set  
**''Feb 5'': Run existing data set  
''From there, we will identify a weekly milestone pertaining to results to ensure results are as visible and actionable as possible''
''From there, we will identify a weekly milestone pertaining to results to ensure results are as visible and actionable as possible''
** Dec 12th e10s Telemetry probe triage: [https://docs.google.com/spreadsheets/d/1FIaGNv1q750mo9S7cJJY_8erbiF7j9snyX8Yd0diAbA/edit#gid=307269420 spreadsheet]
** {{bug|1182637}}: the BHR/event-loop-lag responsiveness regression in e10s has been confirmed first-hand with an extension that visualizes the BHR jank measurements: https://github.com/chutten/statuser
*** BHR reporting still needs to be improved to narrow down the origins: {{bug|1224374}}
** There also appears to be a stability regression https://bugzilla.mozilla.org/show_bug.cgi?id=1229104#c19
** There is also a known regression in e10s page-load speed in Talos & Telemetry data
** Telemetry E10S Measurement Meta {{Bug|1222849}}
** Performance Tracker Meta {{Bug|1198187}}


==Add-Ons + WebExtensions==
==Add-Ons + WebExtensions==
canmove, Confirmed users, Bureaucrats and Sysops emeriti
5,401

edits