Firefox OS/Performance/Release Acceptance: Difference between revisions
< Firefox OS | Performance
Jump to navigation
Jump to search
m (Lakrits moved page FirefoxOS/Performance/Release Acceptance to Firefox OS/Performance/Release Acceptance: The official spelling of "Firefox OS" leaves a space between the two parts of the name. It's easier to find a page if the spelling of its...) |
Bobbychien (talk | contribs) (→2.2: update Time table) |
||
| Line 13: | Line 13: | ||
''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.'' | ''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.5 == | |||
* Reference Device: Flame-KK 319MB and Aries-KK | |||
* Reference Workload: Light | |||
{| class="wikitable" | |||
|- | |||
! Application !! [http://raptor.mozilla.org/#/dashboard/script/apps.js?device=flame-kk&branch=master&memory=319&series=coldlaunch.* Time] !! First Launch Memory <!-- Relaunch !! Max Memory !! Max Power --> | |||
|- | |||
| Calendar || [http://raptor.mozilla.org/#/dashboard/script/apps.js?device=flame-kk&branch=master&memory=319&series=coldlaunch.*&panelId=1&fullscreen 1150 ms] | |||
|- | |||
| Camera || [http://raptor.mozilla.org/#/dashboard/script/apps.js?device=flame-kk&branch=master&memory=319&series=coldlaunch.*&panelId=2&fullscreen 1550 ms] | |||
|- | |||
| Clock || [http://raptor.mozilla.org/#/dashboard/script/apps.js?device=flame-kk&branch=master&memory=319&series=coldlaunch.*&panelId=3&fullscreen 1000 ms] | |||
|- | |||
| Contacts || [http://raptor.mozilla.org/#/dashboard/script/apps.js?device=flame-kk&branch=master&memory=319&series=coldlaunch.*&panelId=4&fullscreen 1000 ms] | |||
|- | |||
| Dialer || [http://raptor.mozilla.org/#/dashboard/script/apps.js?device=flame-kk&branch=master&memory=319&series=coldlaunch.*&panelId=10&fullscreen 1000 ms] | |||
|- | |||
| Email || [http://raptor.mozilla.org/#/dashboard/script/apps.js?device=flame-kk&branch=master&memory=319&series=coldlaunch.*&panelId=5&fullscreen 1000 ms] | |||
|- | |||
| FM Radio || [http://raptor.mozilla.org/#/dashboard/script/apps.js?device=flame-kk&branch=master&memory=319&series=coldlaunch.*&panelId=6&fullscreen 1000 ms] | |||
|- | |||
| Gallery || [http://raptor.mozilla.org/#/dashboard/script/apps.js?device=flame-kk&branch=master&memory=319&series=coldlaunch.*&panelId=7&fullscreen 1000 ms] | |||
|- | |||
| Music || [http://raptor.mozilla.org/#/dashboard/script/apps.js?device=flame-kk&branch=master&memory=319&series=coldlaunch.*&panelId=9&fullscreen 1000 ms] | |||
|- | |||
| Settings || [http://raptor.mozilla.org/#/dashboard/script/apps.js?device=flame-kk&branch=master&memory=319&series=coldlaunch.*&panelId=11&fullscreen 2600 ms] | |||
|- | |||
| SMS || [http://raptor.mozilla.org/#/dashboard/script/apps.js?device=flame-kk&branch=master&memory=319&series=coldlaunch.*&panelId=8&fullscreen 1200 ms] | |||
|- | |||
| Video || [http://raptor.mozilla.org/#/dashboard/script/apps.js?device=flame-kk&branch=master&memory=319&series=coldlaunch.*&panelId=12&fullscreen 1000 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].'' | |||
== 2.2 == | == 2.2 == | ||
Revision as of 03:15, 27 July 2015
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.5
- Reference Device: Flame-KK 319MB and Aries-KK
- Reference Workload: Light
| Application | Time | First Launch Memory |
|---|---|---|
| Calendar | 1150 ms | |
| Camera | 1550 ms | |
| Clock | 1000 ms | |
| Contacts | 1000 ms | |
| Dialer | 1000 ms | |
| 1000 ms | ||
| FM Radio | 1000 ms | |
| Gallery | 1000 ms | |
| Music | 1000 ms | |
| Settings | 2600 ms | |
| SMS | 1200 ms | |
| Video | 1000 ms |
NOTE: These apps have been instrumented to emit events that support timing their launch states.
2.2
- Reference Device:
- Reference Workload: Light
ADD NEW 2.2 TEST DATA at here
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 | 1150 ms | |
| Camera | 1550 ms | |
| Clock | 1000 ms | |
| Contacts | 1000 ms | |
| Cost Control | 1000 ms | |
| Dialer | 1000 ms | |
| 1000 ms | ||
| FM Radio | 1000 ms | |
| Gallery | 1000 ms | |
| Homescreen | 1000 ms | |
| Marketplace | 1000 ms | |
| Music | 1000 ms | |
| Settings | 2600 ms | |
| SMS | 1200 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 |
| 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 |
| 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.