Firefox OS/Performance/Automation/Subsequent Launch Latency: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
No edit summary
Line 158: Line 158:
| '''Gallery''' || TBD || Bug || Bug || Bug || Bug
| '''Gallery''' || TBD || Bug || Bug || Bug || Bug
|-
|-
| '''Marketplace''' || TBD || {{bug|837668}} || Bug || Bug || Bug || Bug || Bug
| '''Marketplace''' || TBD || Bug || Bug || Bug || Bug
|-
|-
| '''Music''' || TBD || Bug || Bug || Bug || Bug
| '''Music''' || TBD || Bug || Bug || Bug || Bug

Revision as of 13:05, 23 July 2014

Subsequent Launch Latency

Summary

Measures elapsed time from a launch of an application already in memory to a series of defined startup events.

Usage

Test Cases

Launch each of the following apps from a warm state:

  • Browser
  • Calendar
  • Camera
  • Clock
  • Contacts
  • Dialer
  • Email
  • FM Radio
  • Gallery
  • Marketplace
  • Music
  • Settings
  • SMS
  • Template
  • Usage
  • Video

For each app, report the time elapsed to the following events:

  • moz-chrome-dom-loaded
  • moz-chrome-interactive
  • moz-app-visually-complete
  • moz-content-interative
  • moz-app-loaded

Precision

TBD

How to Run On-Demand

TBD

Published Results

FxOS 2.0

Flame
startup_>_moz-chrome-dom-loaded
startup_>_moz-chrome-interactive
startup_>_moz-app-visually-complete
startup_>_moz-content-interative
startup_>_moz-app-loaded

FxOS 2.1

Flame
startup_>_moz-chrome-dom-loaded
startup_>_moz-chrome-interactive
startup_>_moz-app-visually-complete
startup_>_moz-content-interative
startup_>_moz-app-loaded

References

Development

Design

These tests use the same workload and instrumentation as the Launch Latency tests.

Common Setup

  1. Restart B2G Process
  2. Invoke launch programmatically
  3. Close app

All Cases

  1. Invoke launch programmatically
  2. Inject the Performance Helper and save start time
  3. App instrumentation throws timeline events at appropriate times
  4. Performance helper observes events
  5. Event emit times are compared with start time for time elapsed

Results

  • Result is time elapsed to each event
  • Execute test 30 times, for each event report mean, median, deviation

Project Roadmap

Overview

  • Lead: Eli Perelman
  • Tracking Bug: TBD
Milestone 1: Design
Test Design Validity Review
All Cases Bug Bug
Milestone 2: Test Milestone 3: Publication
Availability On-Demand Test Results Review Published Results Documentation
Browser TBD Bug Bug Bug Bug
Calendar TBD Bug Bug Bug Bug
Camera TBD Bug Bug Bug Bug
Clock TBD Bug Bug Bug Bug
Contacts TBD Bug Bug Bug Bug
Dialer TBD Bug Bug Bug Bug
Email TBD Bug Bug Bug Bug
FM Radio TBD Bug Bug Bug Bug
Gallery TBD Bug Bug Bug Bug
Marketplace TBD Bug Bug Bug Bug
Music TBD Bug Bug Bug Bug
Settings TBD Bug Bug Bug Bug
SMS TBD Bug Bug Bug Bug
Template TBD Bug Bug Bug Bug
Usage TBD Bug Bug Bug Bug
Video TBD Bug Bug Bug Bug

template

Retrieved from "https://wiki.allizom.org/index.php?title=Firefox_OS/Performance/Automation/Subsequent_Launch_Latency&oldid=999514"