Firefox OS/Performance/Release Acceptance: Difference between revisions

From MozillaWiki
Jump to navigation Jump to search
(Removed Homescreen from 2.0 as further changes to 2.0 introduces risk too late in the release cycle.)
Line 18: Line 18:
* Reference Device: Flame 319MB
* Reference Device: Flame 319MB
* Reference Workload: Light
* Reference Workload: Light
* For Camera App, as discussed with the PM, the performance boundary will be based on the average of 3 performance runs done in Oct 2nd, 21st, and 30th.  If the number regresses more than 100ms from the criteria, it will be considered as a regression.


{| class="wikitable"
{| class="wikitable"
Line 25: Line 26:
| Calendar || [https://datazilla.mozilla.org/b2g/?branch=master&device=flame-319MB&range=7&test=startup_%3E_moz-app-visually-complete&app_list=calendar&app=calendar&plot=median 1000 ms]
| Calendar || [https://datazilla.mozilla.org/b2g/?branch=master&device=flame-319MB&range=7&test=startup_%3E_moz-app-visually-complete&app_list=calendar&app=calendar&plot=median 1000 ms]
|-
|-
| Camera || [https://datazilla.mozilla.org/b2g/?branch=master&device=flame-319MB&range=7&test=startup_%3E_moz-app-visually-complete&app_list=camera&app=camera&plot=median 1000 ms]
| Camera || [https://datazilla.mozilla.org/b2g/?branch=master&device=flame-319MB&range=7&test=startup_%3E_moz-app-visually-complete&app_list=camera&app=camera&plot=median 1550 ms]
|-
|-
| Clock || [https://datazilla.mozilla.org/b2g/?branch=master&device=flame-319MB&range=7&test=startup_%3E_moz-app-visually-complete&app_list=clock&app=clock&plot=median 1000 ms]
| Clock || [https://datazilla.mozilla.org/b2g/?branch=master&device=flame-319MB&range=7&test=startup_%3E_moz-app-visually-complete&app_list=clock&app=clock&plot=median 1000 ms]
Line 53: Line 54:


''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].''
''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].''


== 2.0 ==
== 2.0 ==

Revision as of 20:16, 7 November 2014

Criteria

Definitions

First Launch
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. These timings are captured to the moz-app-visually-complete event documented on MDN.
First Launch Memory
Maximum bytes of RAM used by an application after completing its First Launch.
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 Launch values are calculated from 30 such iterations.

2.1

  • Reference Device: Flame 319MB
  • Reference Workload: Light
  • For Camera App, as discussed with the PM, the performance boundary will be based on the average of 3 performance runs done in Oct 2nd, 21st, and 30th. If the number regresses more than 100ms from the criteria, it will be considered as a regression.
Application First Launch First Launch Memory
Calendar 1000 ms
Camera 1550 ms
Clock 1000 ms
Contacts 1000 ms
Cost Control 1000 ms
Dialer 1000 ms
Email 1000 ms
FM Radio 1000 ms
Gallery 1000 ms
Homescreen 1000 ms
Marketplace 1000 ms
Settings 1000 ms
SMS 1000 ms
Video 1000 ms

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

2.0

  • Reference Device: Flame 319MB
  • Reference Workload: Light
Application First Launch
Calendar 1000 ms
Camera 1000 ms
Clock 1000 ms
Contacts 1000 ms
Cost Control 1000 ms
Dialer 1000 ms
Email 1000 ms
FM Radio 1000 ms
Gallery 1000 ms
Marketplace 1000 ms
Settings 1000 ms
SMS 1000 ms
Video 1000 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 First Launch
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.