Firefox OS/Performance/Automation/Memory Consumption: Difference between revisions
< Firefox OS | Performance | Automation
Jump to navigation
Jump to search
Line 3: | Line 3: | ||
== Summary == | == Summary == | ||
Measures memory consumption | Measures memory consumption in several test scenarios to detect abnormal memory usage patterns. | ||
==== Memory usage parameters ==== | |||
{| border="1" | |||
|- | |||
!Parameter !! Description | |||
|- | |||
| VSS || Virtual set size | |||
|- | |||
| RSS || Resident set size | |||
|- | |||
| USS || Unique set size | |||
|- | |||
| PSS || Proportional set size | |||
|- | |||
|} | |||
== Test cases == | |||
=== Startup Memory Consumption === | |||
= | * '''Lead:''' Wander Lairson Costa | ||
* '''Tracking Bug:''' [http://bugzilla.mozilla.org/show_bug.cgi?id=1044297 1044297] | |||
Measures memory consumption of the application and b2g process after [https://developer.mozilla.org/en-US/Apps/Build/Performance/Firefox_OS_app_responsiveness_guidelines moz-app-loaded event]. | |||
Launch each of the following apps: | Launch each of the following apps: | ||
Line 28: | Line 49: | ||
* Video | * Video | ||
For each app, report the the memory usage after the moz-app-loaded event, for both the app and b2g process. | For each app, report the the memory usage after the moz-app-loaded event, for both the app and b2g process. Below you can see a flowchart of the test case: | ||
=== Precision === | [[File:Moz-app-load-mem-test.jpg|600x600px|framed|center|Flowchart of the startup memory test]] | ||
==== Precision ==== | |||
TBD | TBD | ||
=== How to Run On-Demand === | ==== How to Run On-Demand ==== | ||
TBD | TBD | ||
=== Published Results === | ==== Published Results ==== | ||
TBD | TBD | ||
== Development == | == Development == | ||
Line 52: | Line 71: | ||
=== Design === | === Design === | ||
==== Common Setup ==== | ==== Common Setup ==== | ||
Line 74: | Line 78: | ||
==== All Cases ==== | ==== All Cases ==== | ||
# Invoke launch programmatically | # Invoke launch programmatically | ||
# Inject the Performance Helper | # Inject the Performance Helper | ||
# App instrumentation throws timeline events at appropriate times | # App instrumentation throws timeline events at appropriate times | ||
Line 89: | Line 93: | ||
=== Project Roadmap === | === Project Roadmap === | ||
{| class="wikitable" | {| class="wikitable" | ||
Line 96: | Line 98: | ||
! colspan="2" | Milestone 1: Design | ! colspan="2" | Milestone 1: Design | ||
|- | |- | ||
! | ! | ||
! Test Design | ! Test Design | ||
! Validity Review | ! Validity Review | ||
Line 104: | Line 106: | ||
|} | |} | ||
== References == | |||
* [http://www.akkadia.org/drepper/cpumemory.pdf What every programmer should know about memory] | |||
* [http://sealedabstract.com/rants/why-mobile-web-apps-are-slow/ Why mobile web apps are slow] | |||
* [https://developer.mozilla.org/en-US/Apps/Build/Performance/Firefox_OS_app_responsiveness_guidelines Firefox OS App Responsiveness Guidelines] | |||
<small>[http://wiki.mozilla.org/FirefoxOS/Performance/Automation/Memory_Consumption]</small> | <small>[http://wiki.mozilla.org/FirefoxOS/Performance/Automation/Memory_Consumption]</small> |
Revision as of 12:15, 14 August 2014
Memory Consumption
Summary
Measures memory consumption in several test scenarios to detect abnormal memory usage patterns.
Memory usage parameters
Parameter | Description |
---|---|
VSS | Virtual set size |
RSS | Resident set size |
USS | Unique set size |
PSS | Proportional set size |
Test cases
Startup Memory Consumption
- Lead: Wander Lairson Costa
- Tracking Bug: 1044297
Measures memory consumption of the application and b2g process after moz-app-loaded event.
Launch each of the following apps:
- Browser
- Calendar
- Camera
- Clock
- Contacts
- Dialer
- FM Radio
- Gallery
- Marketplace
- Music
- Settings
- SMS
- Template
- Usage
- Video
For each app, report the the memory usage after the moz-app-loaded event, for both the app and b2g process. Below you can see a flowchart of the test case:
Precision
TBD
How to Run On-Demand
TBD
Published Results
TBD
Development
Design
Common Setup
- Set up workload
- Restart B2G process
All Cases
- Invoke launch programmatically
- Inject the Performance Helper
- App instrumentation throws timeline events at appropriate times
- Performance helper observes events
- After moz-app-loaded event grab memory usage parameters for the app and b2g process
Results
- Result is the memory usage summary for app and b2g process.
Results
TBD
Project Roadmap
Milestone 1: Design | ||
---|---|---|
Test Design | Validity Review | |
All Cases | Bug | Bug |