UbuntuPowerManagementTesting

Differences between revisions 5 and 6
⇤ ← Revision 5 as of 2010-01-12 12:20:58 →
Size: 2363
Editor: eth0
Comment:
← Revision 6 as of 2010-01-12 13:11:01 → ⇥
Size: 2366
Editor: eth0
Comment:
Deletions are marked like this. Additions are marked like this.
Line 7: Line 7:
* Idle tests 1. Idle tests
Line 17: Line 17:
* HW-specific testing 1. HW-specific testing
Line 46: Line 46:
* Usecase testing 1. Usecase testing

Typical tests should last 30-60s to encapsulate most low-level periodic wakeups[1]. All the tests are to be done on battery (obviously)

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 (full brightness and half brightness)
  • 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

1. 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
    • 3G modem
      • Idle
      • Disconnected
      • Active
        • Similar to WLAN tests
    • Bluetooth
      • Idle
      • Disconnected
      • Active
        • Similar to WLAN tests
    • Additional INFO required: AP model
  • Display tests
    • Test idle with
      • full screen brightness
      • half brightness
  • Backlight measurements
    • Figure out usecase for backlight measurements (Useful for figuring out how agressive ALS should be)

1. Usecase testing

  • Browsing over WLAN
    • Preconfigured with flash plugin at full brightness
    • 5-10 tabs loading a pre-cached set of webpages
      • Loading live sites changes the numbers (due to flash content and changing network conditions)
    • separate tests for browsing over 3G?
  • Music streaming over WLAN
    • Exercises the audio chip, important for ARM platforms that might use a separate DSP
    • Active
      • Peak and average consumption
    • Idle
      • Does the audio chip power off

[1] Longer tests can be considered if we have certain applications that have much longer cycles of periodic activity

CategoryHomepage

AmitKucheria/UbuntuPowerManagementTesting (last edited 2010-09-24 09:41:47 by a91-154-124-12)