Confirmed users
356
edits
E10s/Status/Dec17: Difference between revisions
→Why yellow? e10s is designated 'yellow' or 'at risk' because:
| Line 28: | Line 28: | ||
*** This experiment is going to be run until January 11th (tentative end date) | *** This experiment is going to be run until January 11th (tentative end date) | ||
** Dec 12th e10s Telemetry probe triage: [https://docs.google.com/spreadsheets/d/1FIaGNv1q750mo9S7cJJY_8erbiF7j9snyX8Yd0diAbA/edit#gid=307269420 spreadsheet] | ** 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 | ** {{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 | ||
** There also appears to be a stability regression https://bugzilla.mozilla.org/show_bug.cgi?id=1229104#c19 | |||
*** BHR reporting still needs to be improved to narrow down the origins: {{bug|1224374}} | *** BHR reporting still needs to be improved to narrow down the origins: {{bug|1224374}} | ||
** There is also a known regression in e10s page-load speed in Talos & Telemetry data | ** There is also a known regression in e10s page-load speed in Talos & Telemetry data | ||