Firefox OS/Performance/Release Acceptance: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
(→‎2.0: Added link to email Datazilla graph)
Line 43: Line 43:
| SMS || 1250 ms
| SMS || 1250 ms
|}
|}
''NOTE: These apps have been [https://bugzilla.mozilla.org/show_bug.cgi?id=996038#user_story_header instrumented] to emit events that support timing their [https://developer.mozilla.org/en-US/Apps/Build/Performance/Firefox_OS_app_responsiveness_guidelines#wiki-document-head launch states].''


== 1.4 ==
== 1.4 ==

Revision as of 19:38, 1 July 2014

Criteria

Definitions

Cold Launch Time
Milliseconds elapsed from the user-initiated launch of a not-already-in-memory app to the stable display of that app and its visible content.
Reference Workload
A standardized collection of application data preloaded before the test is run.

Note: All measurements are the median results calculated from multiple iterations of relevant tests. For example, Datazilla's App Cold Launch values are calculated from 30 such iterations.

2.0

  • Reference Device: Flame
  • Reference Workload: Medium
Application Cold Launch Time
Browser 1250 ms
Camera 1250 ms
Contacts 1250 ms
Dialer 1250 ms
Email 1250 ms
Gallery 1250 ms
Marketplace 1250 ms
Settings 1250 ms
SMS 1250 ms

NOTE: These apps have been instrumented to emit events that support timing their launch states.

1.4

  • Reference Device: Buri/Hamachi
  • Reference Workload: Medium
Application Cold Launch Time
Browser No regression since 1.3
Camera No regression since 1.3
Contacts No regression since 1.3
Dialer No regression since 1.3
Email No regression since 1.3
Gallery No regression since 1.3
Marketplace No regression since 1.3
Settings No regression since 1.3
SMS No regression since 1.3

1.3T

  • Reference Device: Tarako

Acceptance for 1.3T will be determined by reviewing final performance results which will include cold launch time.