Closed
Bug 1045938
Opened 10 years ago
Closed 9 years ago
meta: fxOS: Boot Timing Automation
Categories
(Firefox OS Graveyard :: Performance, defect, P2)
Tracking
(tracking-b2g:backlog)
RESOLVED
FIXED
| tracking-b2g | backlog |
People
(Reporter: mlee, Assigned: jbailey, Mentored)
References
()
Details
(Keywords: meta, perf, Whiteboard: [c=boot p= s= u=2.1])
User Story
Our fxOS Performance team wants to track where time is being spent during the OS' boot sequence. To do this we need to track timing for the various stages outlined below: Desired but not required: Power-on|Restart => Bootloader:start <== Implementation-specific; can be multiple bootloaders Bootloader:start => Linux:start <== HARD; needs vendor support Required: Linux :start => init:start <== uptime command gets timing since boot init :start => b2g:start b2g :start => shell.html :made (browser container) shell.html:made => SystemApp :made (iframe container) SystemApp :made => Homescreen :made (iframe container) Homescreen:made => Homescreen :moz-* [chrome-dom-loaded, chrome-interactive, app-visually-complete, content-interactive, app-loaded] Done: 1. make test-perf can be run from the command line to capture timing for the above stages 2. make test-perf is run automatically for the above tests and reports into Datazilla for fxOS 2.1 3. Datazilla displays a "boot" test with subtests for each stage listed above. 4. Datazilla displays each stage's cumulative time on the same graph.
No description provided.
|
||
Comment 2•9 years ago
|
||
Implemented by Raptor [1]. [1] https://developer.mozilla.org/en-US/docs/Mozilla/Firefox_OS/Automated_testing/Raptor
Status: ASSIGNED → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•