From Fedora Project Wiki
No edit summary |
No edit summary |
||
| (One intermediate revision by the same user not shown) | |||
| Line 8: | Line 8: | ||
# Check that you have ''pm-test-day'' package installed: | # Check that you have ''pm-test-day'' package installed: | ||
#:<pre>$ rpm -q pm-test-day</pre> | #:<pre>$ rpm -q pm-test-day</pre> | ||
For better results disable screensaver, screen dimming/turning off, transition to sleep mode, HDD power savings and cron service. | For better results disable screensaver, screen dimming/turning off, transition to sleep mode, HDD power savings and cron service: | ||
# Disable screensaver (if applicable). | |||
# Disable sleep mode, in Gnome 3: | |||
#:<pre>$ gnome-control-center power</pre> | |||
#* Uncheck "On battery power" | |||
# Disable LCD power savings, in Gnome 3: | |||
#:<pre>$ gnome-control-center screen</pre> | |||
#* Uncheck "Dim screen to save power". | |||
#* Set "Turn off after" to max. value. | |||
# Disable cron: | |||
#:<pre># service crond stop</pre> | |||
# Disable user PM via gconf (and save previous settings), it needs to be run under user who is logged into desktop: | # Disable user PM via gconf (and save previous settings), it needs to be run under user who is logged into desktop: | ||
#:<pre>$ pmtd-pm-user-settings saveoff</pre> | #:<pre>$ pmtd-pm-user-settings saveoff</pre> | ||
#* After the test it is possible to restore the previous settings by using the ''restore'' parameter instead of ''saveoff'' | #* After the test it is possible to restore the previous settings by using the ''restore'' parameter instead of ''saveoff''. | ||
|actions= | |actions= | ||
{{admon/note|This test needs to be run on battery.}} | {{admon/note|This test needs to be run on battery.}} | ||
{{admon/ | {{admon/note|Before running this test please recharge your battery to full capacity.}} | ||
{{admon/note|If it complains that the test cannot be run on your computer, please skip this test.}} | |||
# Enable tuned throughput-performance profile by: | |||
#:<pre># tuned-adm profile throughput-performance</pre> | |||
# Run the following command: | # Run the following command: | ||
#:<pre># pmtd-measure | #:<pre># pmtd-measure-idle</pre> | ||
# Do not touch your computer until the test completes (cca. 15 minutes). | # Do not touch your computer until the test completes (cca. 15 minutes). | ||
# Write the output to the results table. | # Write the output to the results table. | ||
Latest revision as of 23:27, 23 March 2011
Description
This test case measures energy consumed by you system while in active idle with throughput-performance profile activated.
This test targets laptop users.
This test will take approx. 15 minutes.
If you do not have laptop or enough time feel free to skip this test. In this case please leave the corresponding column in the results table blank.
If you complete this test, please also complete the Tuned psave idle test.
Setup
- Check that you have pm-test-day package installed:
$ rpm -q pm-test-day
For better results disable screensaver, screen dimming/turning off, transition to sleep mode, HDD power savings and cron service:
- Disable screensaver (if applicable).
- Disable sleep mode, in Gnome 3:
$ gnome-control-center power
- Uncheck "On battery power"
- Disable LCD power savings, in Gnome 3:
$ gnome-control-center screen
- Uncheck "Dim screen to save power".
- Set "Turn off after" to max. value.
- Disable cron:
# service crond stop
- Disable user PM via gconf (and save previous settings), it needs to be run under user who is logged into desktop:
$ pmtd-pm-user-settings saveoff
- After the test it is possible to restore the previous settings by using the restore parameter instead of saveoff.
How to test
This test needs to be run on battery.
Before running this test please recharge your battery to full capacity.
If it complains that the test cannot be run on your computer, please skip this test.
- Enable tuned throughput-performance profile by:
# tuned-adm profile throughput-performance
- Run the following command:
# pmtd-measure-idle
- Do not touch your computer until the test completes (cca. 15 minutes).
- Write the output to the results table.
Expected Results
- Energy consumed during the test is written to the stdout.