Closed Bug 1079564 Opened 10 years ago Closed 10 years ago

Clock's startup time is over the 1000 ms acceptance threshold for 2.1

Categories

(Firefox OS Graveyard :: Gaia::Clock, defect)

Product:
Firefox OS Graveyard
Component:
Gaia::Clock
Platform:
x86
All
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(tracking-b2g:+)

Status:
RESOLVED WORKSFORME
Project Flags:
tracking-b2g +

People

(Reporter: gmealer, Unassigned)

References

Details

(Keywords: perf, Whiteboard: [priority]) 

[Blocking Requested - why for this release]:

See test results at:

https://wiki.mozilla.org/B2G/QA/2014-10-02_Performance_Acceptance#Clock

Median startup time was 1045 ms for 480 launches. This is also a regression from 2.0, which was median 919 ms for 480 launches. 

Graphs, raw data and other testing details are on the wiki.

This is so close to 1000 ms that I hesitate to file the bug as blocker, but would like an explicit decision so am going to nom regardless.
Depends on: 1059353
Duping to existing bug 1059353 which has some detailed diagnostic info.
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → DUPLICATE
blocking-b2g: 2.1? → ---
Status: RESOLVED → REOPENED
Resolution: DUPLICATE → ---
Whiteboard: [priority]
[priority] --> tracking-b2g:+ conversion
tracking-b2g: --- → +
Clock is back under guidelines as of the 10-20 and 10-31 acceptance tests. Closing this, but will re-open if it goes back over guidelines again in future acceptance tests.
Status: REOPENED → RESOLVED
Closed: 10 years ago → 10 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.