Guest User

Untitled

a guest
Jan 19th, 2016
494
0
Never
Not a member of Pastebin yet? Sign Up, it unlocks many cool features!
text 1.38 KB | None | 0 0
  1. l;dr: we no longer plan to ship e10s to our release population in Firefox
  2. 45
  3.  
  4.  
  5. Several of us just met to go over the data we've collected on the our Beta
  6. 44 e10s experiment and how it relates to our release criteria. There are
  7. three main areas of concern.
  8.  
  9. *Population.* Our plan has been to release e10s first to users who have no
  10. add-ons and no a11y features enabled due to known issues with those two
  11. areas of code. Our crash data from the 44 experiment indicates that we have
  12. both sets of users in the experiment population.
  13.  
  14. *Stability. *Beta 44 with e10s seems to be crashing or hanging roughly 20%
  15. more frequently than Beta 44 without e10s. One of our release criteria is
  16. to not regress the crash and hang rate.
  17.  
  18. *Responsiveness.* Our measure of responsiveness, BHR, shows that users with
  19. e10s enabled are seeing more event loop jank than users without e10s
  20. enabled.
  21.  
  22. For the population issue, we have already landed code in 45 to address
  23. those issues and bugs are filed to shore that up some more. For stability
  24. and responsiveness, we have gathered useful information that we will use to
  25. address those issues. In order to gather even more useful information we
  26. plan to expand our e10s experiment in 45 Beta to 50% of users, meaning that
  27. 50% of users will get e10s turned on if they have no a11y features enabled
  28. and no add-ons installed. The goal now is to target 46 release.
Advertisement
Add Comment
Please, Sign In to add comment