Closed
Bug 1182636
Opened 10 years ago
Closed 9 years ago
Telemetry: startup times are worse in e10s
Categories
(Firefox :: General, defect)
Tracking
()
RESOLVED
WORKSFORME
Tracking | Status | |
---|---|---|
e10s | + | --- |
People
(Reporter: vladan, Unassigned)
References
(Blocks 1 open bug, )
Details
Telemetry numbers imply that the median real-world startup time, measured as time to first-paint, regressed by 550ms or 20% with e10s:
"simpleMeasurements/firstPaint" in http://nbviewer.ipython.org/urls/gist.githubusercontent.com/vitillo/cb6f1304316c1c1a2cbc/raw/e10s%20analysis.ipynb
^ Based on Telemetry collected from Nightly 41 on June 15th, from buildIDs in the range [20150601, 20150616]
Full e10s performance write-up: https://groups.google.com/d/msg/mozilla.dev.platform/elb0Au7qwG0/Yarsx1xrrnwJ
![]() |
||
Updated•10 years ago
|
tracking-e10s:
--- → ?
Updated•10 years ago
|
![]() |
||
Comment 2•9 years ago
|
||
Hey Roberto, do we have updated data for these startup metrics?
Flags: needinfo?(rvitillo)
Comment 3•9 years ago
|
||
Our latest data show that there is no difference in startup time, measured as time to first-paint [1].
[1] https://github.com/vitillo/e10s_analyses/blob/master/aurora/e10s_experiment.ipynb
Flags: needinfo?(rvitillo)
![]() |
||
Comment 4•9 years ago
|
||
great, thanks for the updated report.
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•