Firefox OS/Performance/Memory acceptance criteria: Difference between revisions

Firefox OS/Performance/Memory acceptance criteria (view source)

14 bytes removed , 30 October 2012

187

edits

@@ 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.
-'''MANDATORY''': Every foreground application X does not die within the constraints defined below.
+'''MANDATORY''': A foreground application is never killed due to memory pressure while a perceivable or background application is alive.
-'''MANDATORY''': While any perceivable application X is running, every foreground application Y does not die within the constraints defined below.
+'''MANDATORY''': A perceivable application is never killed due to memory pressure while a background application is alive.
-'''MANDATORY''': While any background application X is running, every perceivable application Y does not die within the constraints defined below.
+'''QoS''': We will strive to maximize the number of perceivable and background applications that stay alive over the workloads defined below, while meeting the mandatory criteria above.  We should reject builds which regress the number of apps that stay alive under our workloads.
-'''QoS''': While meeting the constraints above, maximize the number of perceivable and background applications that stay alive over the workloads defined below.
 (''TODO'': define if or to what extent third-party code can affect these criteria