1404387 - e10s disabled by user; pref maybe needing reset (for 57)

Status: RESOLVED WONTFIX

(Core :: General, enhancement)

Description

[Jonathan Howard]

Over 5% of beta currently have it disabled according to telemetry.
Needs developer to clarify whether non-e10s should still be an option.


https://telemetry.mozilla.org/new-pipeline/evo.html#!aggregates=bucket-2!bucket-3!bucket-4!bucket-5!bucket-6!bucket-7!bucket-8!bucket-9!bucket-10!bucket-11!bucket-12&cumulative=0&end_date=null&keys=&max_channel_version=beta%252F57&measure=E10S_STATUS&min_channel_version=beta%252F57&processType=*&product=Firefox&sanitize=1&sort_keys=submissions&start_date=null&trim=1&use_submission_date=1

Comment 1

[Mike Conley (:mconley) (:⚙️)]

felipe is on PTO, but he might want to look at this next week when he's back. Cc'ing him since needinfo's are blocked.

Comment 2

[Ritu Kothari (:ritu) (Inactive, please n-i to RyanVM, jcristau, or pascal)]

Tracked for now, assuming we want to do something about it in 57.

Comment 3

[Liz Henry (:lizzard) (relman/hg->git project)]

Felipe, just making sure you are aware of this - is there something we need to do here? I believe we are planning to migrate everyone to e10s except for JAWS users.

Comment 4

[:Felipe Gomes (needinfo for replies!)]

Oh I had missed this, thanks for bringing it to my attention. But there's nothing we need to do here. Explanation:

1 - That number is from the beta channel, but on release this is much lower, 0.47% according to https://telemetry.mozilla.org/new-pipeline/dist.html#!cumulative=0&end_date=2017-10-10&keys=__none__!__none__!__none__&max_channel_version=release%252F56&measure=E10S_STATUS&min_channel_version=beta%252F57&processType=parent&product=Firefox&sanitize=1&sort_keys=submissions&start_date=2017-09-28&table=0&trim=1&use_submission_date=1

2 - bug 1406212 will already reset this setting and put everyone on e10s, although that bug is scheduled for 58 only, not 57.  For 57 beta, it's ok to keep running these 5% of people until the a11y decision is reached, and after that decision is made, the extra risk of then doing anything else to reclaim these 5% of people is unnecessary.

3 - There's nothing special needed to do for e10s-a11y, if it indeed gets shipped. It used a separate pref to have e10s disabled (not the general purpose one), and once e10s-a11y it ships, that pref will just be ignored.