1252030 - Examine the long tail of FX_TAB_SWITCH_TOTAL_E10S_MS distribution

Status: NEW

(Core :: General, defect, P3)

Description

[Gabor Krizsanits (INACTIVE)]

https://telemetry.mozilla.org/new-pipeline/dist.html#!cumulative=0&end_date=2016-02-27&keys=__none__!__none__!__none__&max_channel_version=nightly%252F47&measure=FX_TAB_SWITCH_TOTAL_E10S_MS&min_channel_version=null&product=Firefox&sanitize=1&sort_keys=submissions&start_date=2016-01-25&table=0&trim=1&use_submission_date=0

My theory is that this effect is caused by content process janks mainly, but it would be interesting to see if there is any other factor too.

Comment 1

[Gabor Krizsanits (INACTIVE)]

Numbers in general looking good compared to the non-e10s case so I don't think this should be very high prio right now.

Comment 2

[Chris Peterson [:cpeterson]]

Gabor, what are the next steps for this FX_TAB_SWITCH_TOTAL_E10S_MS bug? Should this analysis need to block e10s release?

Comment 3

[Gabor Krizsanits (INACTIVE)]

(In reply to Chris Peterson [:cpeterson] from comment #2)
> Gabor, what are the next steps for this FX_TAB_SWITCH_TOTAL_E10S_MS bug?
> Should this analysis need to block e10s release?

I don't think so. Based on the current numbers this should have quite low priority. P4?

Comment 4

[Chris Peterson [:cpeterson]]

Thanks. We can consider dropping this from P2 to P4 when we start working on tracking-e10s=+ bugs. In the meantime, I will remove this bug from UI Smoothness release criteria (bug 1251547).

Comment 5

[Sylvestre Ledru [:Sylvestre]]

Moving to p3 because no activity for at least 1 year(s).
See https://github.com/mozilla/bug-handling/blob/master/policy/triage-bugzilla.md#how-do-you-triage for more information