Electrolysis/Meetings/2016-02-04: Difference between revisions

Jump to navigation Jump to search
chutten responsiveness
(meeting notes)
(chutten responsiveness)
 
Line 72: Line 72:


Next steps: repeat this analysis excluding people with addons, continue to file and prioritize the content process topcrash list: https://crash-stats.mozilla.com/search/?ActiveExperiment=e10s-beta45-withaddons%40experiments.mozilla.org&process_type=content&_facets=signature&_columns=date&_columns=signature&_columns=product&_columns=version&_columns=build_id&_columns=platform#facet-signature
Next steps: repeat this analysis excluding people with addons, continue to file and prioritize the content process topcrash list: https://crash-stats.mozilla.com/search/?ActiveExperiment=e10s-beta45-withaddons%40experiments.mozilla.org&process_type=content&_facets=signature&_columns=date&_columns=signature&_columns=product&_columns=version&_columns=build_id&_columns=platform#facet-signature
== chutten ==
Responsiveness analysis using preliminary data shows a possible 2% higher rate of janks as measured by BHR in e10s. This number requires further analysis.
Looking at INPUT_EVENT_RESPONSE_MS in {{bug|1223780}} (and, to a lesser extent, the parent-process-only EVENTLOOP_UI_ACTIVITY_MS) shows no obvious trend, so maybe these janks are not user visible.
Checking the distribution of gecko activity as per {{bug|1182637}} shows a dramatic shift to the left as expected after the fix to idle BHR reports .
Note: this is on preliminary data, so it might be skewed by early adopters.
106

edits

Navigation menu