[Blocking Requested - why for this release]: See test results at: https://wiki.mozilla.org/B2G/QA/2014-10-02_Performance_Acceptance#Calendar Median startup time was 1093 ms for 480 launches. There are no 2.0 results to compare to, as the visually-complete test was not enabled on that branch. Graphs, raw data and other testing details are on the wiki. When examining the graph and data, please also note that the startup times are bimodal, which is unusual. That might indicate that there's something during startup that only sometimes happens and slows results. If so, that's what's putting median launch on the wrong side of 1000 ms, so it's worth examining.
Typoed. The wiki link should be: https://wiki.mozilla.org/B2G/QA/2014-10-02_Performance_Acceptance#Music
4 years ago
Jim will investigate to see if we are adding the visually-complete event at the right place
Assignee: nobody → squibblyflabbetydoo
Making this a priority for investigation, but not blocking release since the numbers are close to 1000ms target.
blocking-b2g: 2.1? → ---
You guys may be interested in bug 1069450. That should get you guys back under 1000ms. We're seeking help to find the offending commit as many of us are pretty slammed.
(In reply to Ghislain Aus Lacroix [:aus] from comment #4) > You guys may be interested in bug 1069450. That should get you guys back > under 1000ms. We're seeking help to find the offending commit as many of us > are pretty slammed. We could probably fix this without actually doing anything to perf, since we could be emitting the visually-complete event earlier than we currently are.
Music's time is back under guidelines as of the last couple of acceptance comparisons (this probably reflects the changes in our timing mechanism, but should be more accurate). https://wiki.mozilla.org/B2G/QA/2014-10-31_Performance_Acceptance#Music I'm closing this out, but will re-open later if it slides back outside them.
Status: NEW → RESOLVED
Last Resolved: 3 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.