Closed
Bug 1011577
Opened 10 years ago
Closed 10 years ago
Use new make test-perf cold launch metric as the default view in Datazilla
Categories
(Firefox OS Graveyard :: Gaia::PerformanceTest, defect, P2)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: Eli, Assigned: Eli)
References
Details
(Keywords: perf, Whiteboard: [c=automation p=1 s= u=])
User Story
As an app developer, release manager, quality assurance engineer, partner, and member of the fxOS performance team I need a simple way to track application performance. The Datazilla dashboard provides this but needs to be updated to default to the most critical device configuration and metric we monitor. To achieve this, Datazilla's default view needs to be updated to the following when accessed via https://datazilla.mozilla.org/b2g Test : startup_>_moz-app-visually-complete Time Range : 7 Days Gaia Branch : master Device : flame-319MB The full URL for this view is: https://datazilla.mozilla.org/b2g/?branch=master&device=flame-319MB&range=7&test=startup_%3E_moz-app-visually-complete&app_list=calendar,camera,clock,communications/contacts,communications/dialer,costcontrol,email%20FTU,fm,gallery,settings,sms,video&app=communications/dialer&plot=median
Currently Datazilla uses b2gperf for measuring the cold launch startup times in FFOS Apps. Once bug 996038 lands, there will be new metrics which are ran via `make test-perf`. We will need to switch Datazilla to use this new metric as the default view for FFOS Apps instead of the b2gperf metric.
Assignee | ||
Updated•10 years ago
|
Assignee: nobody → eperelman
Whiteboard: [c=automation p= s= u=] → [c=automation p=1 s= u=]
Assignee | ||
Updated•10 years ago
|
Assignee | ||
Updated•10 years ago
|
Status: NEW → ASSIGNED
Assignee | ||
Comment 1•10 years ago
|
||
Jonathan, could you please add the following new events for display in Datazilla and make the 'moz-content-interactive' metric the default view for B2G? 'startup > moz-chrome-dom-loaded' 'startup > moz-chrome-interactive' 'startup > moz-app-visually-complete' 'startup > moz-content-interactive' 'startup > moz-app-loaded'
Flags: needinfo?(jeads)
Assignee | ||
Comment 2•10 years ago
|
||
Actually, we are going to hold off on this until we have more apps triggering the events.
Flags: needinfo?(jeads)
Assignee | ||
Comment 3•10 years ago
|
||
As a revision to comment 1, we are instead going to be using 'moz-app-visually-complete' as the default view instead of 'moz-content-interactive'.
Assignee | ||
Comment 4•10 years ago
|
||
The plan is for this to go live this sprint. The default view will be: Test: startup_>_moz-app-visually-complete Time Range: 7 Days Gaia Branch: master Device: flame-512MB We are awaiting some final app changes and then we can go live with this.
Comment 5•10 years ago
|
||
Default Device should be flame-319MB. We need everyone to be aware of performance on our lowest spec configuration.
User Story: (updated)
Assignee | ||
Comment 6•10 years ago
|
||
Sounds good Mike, thanks.
Updated•10 years ago
|
Status: ASSIGNED → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•