Confirmed users
699
edits
Firefox OS/Performance/Memory acceptance criteria: Difference between revisions
Firefox OS/Performance/Memory acceptance criteria (view source)
Revision as of 21:31, 26 November 2012
, 26 November 2012→Criteria
| Line 31: | Line 31: | ||
application Y must be loaded and its user interface brought to the foreground. Application X must remain loaded while Y is in the foreground. When application Y returns data to X, X's user interface must be brought to the foreground. | application Y must be loaded and its user interface brought to the foreground. Application X must remain loaded while Y is in the foreground. When application Y returns data to X, X's user interface must be brought to the foreground. | ||
'''MANDATORY''': | '''MANDATORY''': No foreground application is killed due to memory pressure while a perceivable or background application is alive. | ||
'''MANDATORY''': | '''MANDATORY''': No perceivable application is killed due to memory pressure while a background application is alive. | ||
'''QoS''': | '''QoS''': The number of perceivable and background applications that stay alive over the workloads defined below does not regress, while meeting the mandatory criteria above. Informally, a best effort is made to maximize the number of background and perceivable applications that stay alive. Builds that regress the number of apps that stay alive under our workloads are rejected. | ||
(''TODO'': define if or to what extent third-party code can affect these criteria | (''TODO'': define if or to what extent third-party code can affect these criteria | ||