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

From MozillaWiki
Jump to navigation Jump to search
No edit summary
Line 90: Line 90:
=== Design ===
=== Design ===


=== Setup ===
==== Common Setup ====
# Restart B2G process
# Restart B2G process


=== Test ===  
==== All Cases ====
# Invoke launch programmatically  
# Invoke launch programmatically  
# Inject the Performance Helper and save start time
# Inject the Performance Helper and save start time
# Instrumented throws timeline events at appropriate times
# App instrumentation throws timeline events at appropriate times
# Performance helper observes events
# Performance helper observes events
# Event emit times are compared with start time for time elapsed
# Event emit times are compared with start time for time elapsed


=== Execution ===
* Test should be executed 30 times, report average, median, error
# Test should be executed 30 times, take average and median


== Roadmap ==
== Roadmap ==

Revision as of 12:20, 23 July 2014

Launch Latency

Summary

Measures elapsed time from the first launch of an application to a series of defined startup events.

Usage

Test Cases

Launch each of the following apps from a cold 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 Datazilla
startup_>_moz-chrome-interactive Datazilla
startup_>_moz-app-visually-complete Datazilla
startup_>_moz-content-interative Datazilla
startup_>_moz-app-loaded Datazilla

FxOS 2.1

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

References

Development

Design

Common Setup

  1. Restart B2G process

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
  • Test should be executed 30 times, report average, median, error

Roadmap

Overview

  • Lead: Eli Perelman
  • Tracking Bug: TBD

Milestone 1: Design

Tracking Bug: TBD

Target Release Test Design Validity Review
All TBD Bug Bug

Milestone 2: Test

Tracking Bug: TBD

Target Release Instrumentation Workload Single-run test Results Review Available
Browser TBD bug 837668 Bug Bug Bug
Calendar TBD bug 837671 Bug Bug Bug
Camera TBD bug 1015385 N/A Bug Bug
Clock TBD bug 837668 N/A Bug Bug
Contacts TBD bug 1015388 Light Bug Bug
Dialer TBD bug 837668 Light Bug Bug
Email TBD bug 837677 Bug Bug Bug
FM Radio TBD bug 1015412 Bug Bug Bug
Gallery TBD bug 837674 Light Bug Bug
Marketplace TBD bug 837668 Bug Bug Bug
Music TBD bug 837675 Bug Bug Bug
Settings TBD bug 1015405 N/A Bug Bug
SMS TBD bug 1015390 Light Bug Bug
Template TBD bug 1015391 N/A Bug Bug
Usage TBD bug 837678 Bug Bug Bug
Video TBD bug 837658 N/A Bug Bug

Milestone 3: Publication

Tracking Bug: TBD

Target Release Published Results Documentation Available
Browser TBD Bug Bug
Calendar TBD Bug Bug
Camera TBD Bug Bug
Clock TBD Bug Bug
Contacts TBD Bug Bug
Dialer TBD Bug Bug
Email TBD Bug Bug
FM Radio TBD Bug Bug
Gallery TBD Bug Bug
Marketplace TBD Bug Bug
Music TBD Bug Bug
Settings TBD Bug Bug
SMS TBD Bug Bug
Template TBD Bug Bug
Usage TBD Bug Bug
Video TBD Bug Bug

template

Retrieved from "https://wiki.mozilla.org/index.php?title=Firefox_OS/Performance/Automation/Launch_Latency&oldid=999474"