UbuntuPowerManagementTesting

Differences between revisions 3 and 4
⇤ ← Revision 3 as of 2010-01-12 12:04:33 →
Size: 1881
Editor: eth0
Comment:
← Revision 4 as of 2010-01-12 12:14:01 → ⇥
Size: 2144
Editor: eth0
Comment:
Deletions are marked like this. Additions are marked like this.
Line 5: Line 5:
Typical tests should last 30-60s to encapsulate most low-level periodic wakeups[1]. Typical tests should last 30-60s to encapsulate most low-level periodic wakeups[1]. All the tests are to be done on battery (obviously)
Line 9: Line 9:
    * Boot up default install, wait a minute or so to let all applets to settle down (e.g. 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 (full brightness and half brightness)
Line 21: Line 21:
       * Connect to AP, do network activity for a while and then idle
       * Does the WLAN device switch to low-power mode?		   * Connect to AP, do network activity for a while and then idle
        * Does the WLAN device switch to low-power mode?
Line 24: Line 24:
       * 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		   * 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
Line 27: Line 27:
       * Measure peak consumption and average consumption with activity over WLAN   * Measure peak consumption and average consumption with activity over WLAN
Line 32: Line 32:
       * Similar to WLAN tests   * Similar to WLAN tests
Line 37: Line 37:
       * Similar to WLAN tests   * Similar to WLAN tests
Line 43: Line 43:
* Figure out usecase for backlight measurements   * Backlight measurements
    * Figure out usecase for backlight measurements (Useful for figuring out how agressive ALS should be)
Line 46: Line 47:
  * Browsing
    * Preconfigured with flash plugin		   * Browsing over WLAN
    * Preconfigured with flash plugin at full brightness
Line 49: Line 50:
      * Loading live sites changes the numbers (due to flash)
  * separate tests over WLAN and 3G?		       * Loading live sites changes the numbers (due to flash content and changing network conditions)
   * separate tests for browsing over 3G?
  *

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

* 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

* 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)

* 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?

[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)