UbuntuPowerManagementTesting
Differences between revisions 2 and 3
1434
Comment:
|
1881
|
Deletions are marked like this. | Additions are marked like this. |
Line 9: | Line 9: |
* Boot up default install, wait a minute or so to let all applet to settle down (network connection WLAN) and then measure | * Boot up default install, wait a minute or so to let all applets to settle down (e.g. WLAN) and then measure |
Line 15: | Line 15: |
* server is expected to consume the least and will supply the baseline for a specific HW device | * server is expected to consume the least and will supply the baseline for a specific HW platform |
Line 19: | Line 19: |
* WLAN idle * Connect to AP, do network activity for a while and then idle * Does the WLAN device switch to low-power mode? |
* WLAN * Idle * Connect to AP, do network activity for a while and then idle * Does the WLAN device switch to low-power mode? * Disconnected * Disconnected from AP using applet and make sure we go back to base consumption (radio being turned off correctly) * Use rfkill switch and make sure radio is being turned off correctly * Active * Measure peak consumption and average consumption with activity over WLAN |
Line 23: | Line 29: |
* Same as WLAN | * Idle * Disconnected * Active * Similar to WLAN tests |
Line 25: | Line 34: |
* Same as WLAN | * Idle * Disconnected * Active * Similar to WLAN tests |
Typical tests should last 30-60s to encapsulate most low-level periodic wakeups[1].
* Idle tests
- Idle after boot
- Boot up default install, wait a minute or so to let all applets to settle down (e.g. WLAN) and then measure
- Idle after resume from suspend
- Same as idle after boot
- Idle after resume from hibernate
- Same as idle after boot
- Separate testing for server, desktop and UNR install
- server is expected to consume the least and will supply the baseline for a specific HW platform
* HW-specific testing
- Radio tests
- WLAN
- Idle
- Connect to AP, do network activity for a while and then idle
- Does the WLAN device switch to low-power mode?
- Disconnected
- Disconnected from AP using applet and make sure we go back to base consumption (radio being turned off correctly)
- Use rfkill switch and make sure radio is being turned off correctly
- Active
- Measure peak consumption and average consumption with activity over WLAN
- Idle
- 3G modem
- Idle
- Disconnected
- Active
- Similar to WLAN tests
- Bluetooth
- Idle
- Disconnected
- Active
- Similar to WLAN tests
- Additional INFO required: AP model
- WLAN
- Display tests
- Test idle with
- full screen brightness
- half brightness
- Test idle with
* Figure out usecase for backlight measurements
* Usecase testing
- Browsing
- Preconfigured with flash plugin
- 5-10 tabs loading a pre-cached set of webpages
- Loading live sites changes the numbers (due to flash)
- separate tests over WLAN and 3G?
[1] Longer tests can be considered if we have certain applications that have much longer cycles of periodic activity
AmitKucheria/UbuntuPowerManagementTesting (last edited 2010-09-24 09:41:47 by a91-154-124-12)