canmove, Confirmed users, Bureaucrats and Sysops emeriti
5,401
edits
E10s/Status/April8: Difference between revisions
→e10s Update: March 29
(Created page with "thumbnail|left<br> =e10s Update: '''March 29'''= ==Executive Summary== * Overall, the phase of the project we currently in is best described as Converg...") |
|||
| Line 1: | Line 1: | ||
[[File:Yellow-sm.jpg|thumbnail|left]]<br> | [[File:Yellow-sm.jpg|thumbnail|left]]<br> | ||
=e10s Update: ''' | =e10s Update: '''April 8'''= | ||
==Executive Summary== | ==Executive Summary== | ||
* Overall, the phase of the project we currently in is best described as Convergence. For Firefox 47, the most likely scenario will be that we continue to conduct A/B Experiments in our beta channel until we can [https://bugzilla.mozilla.org/show_bug.cgi?id=1259512 lower our rate of main process, content, and Plugin crashes]. Our latest A/B experiment derived data set indicates we have work to do on stability before we're ready to ship to beta. We are, however, hitting our goals in many areas of our [https://wiki.mozilla.org/Electrolysis/Release_Criteria release criteria] such as Page Load, Startup/Shutdown time, and Scrolling. We still have work to do in areas such as UI Smoothness, Plugin Jank, Memory Usage, and GFX Performance but not to the level that would necessarily block beta. We have made excellent progress in our cadence of deploying A/B experiments and quickly ascertaining the data so we have hit a place where we are tightly coordinated and people are empowered with the right data to move on issues swiftly. Another important thing to note is that we are currently using the System Add-On to deploy our A/B experiments so we are testing the mechanism we designed to ship e10s rather than using experiment code. The current experiment (add-ons + ally = no, apz= yes) will end later this week, in time for Beta 7 and we will have updated results soon thereafter. | * Overall, the phase of the project we currently in is best described as Convergence. For Firefox 47, the most likely scenario will be that we continue to conduct A/B Experiments in our beta channel until we can [https://bugzilla.mozilla.org/show_bug.cgi?id=1259512 lower our rate of main process, content, and Plugin crashes]. Our latest A/B experiment derived data set indicates we have work to do on stability before we're ready to ship to beta. We are, however, hitting our goals in many areas of our [https://wiki.mozilla.org/Electrolysis/Release_Criteria release criteria] such as Page Load, Startup/Shutdown time, and Scrolling. We still have work to do in areas such as UI Smoothness, Plugin Jank, Memory Usage, and GFX Performance but not to the level that would necessarily block beta. We have made excellent progress in our cadence of deploying A/B experiments and quickly ascertaining the data so we have hit a place where we are tightly coordinated and people are empowered with the right data to move on issues swiftly. Another important thing to note is that we are currently using the System Add-On to deploy our A/B experiments so we are testing the mechanism we designed to ship e10s rather than using experiment code. The current experiment (add-ons + ally = no, apz= yes) will end later this week, in time for Beta 7 and we will have updated results soon thereafter. | ||