PC power management

From Infogalactic: the planetary knowledge core
Jump to: navigation, search

Lua error in package.lua at line 80: module 'strict' not found.

PC power management refers to the mechanism for controlling the power use of personal computer hardware. This is typically through the use of software that puts the hardware into the lowest power demand state available. It is an aspect of Green computing.

A typical office PC might use on the order of 90 watts when active (approximately 50 watts for the base unit, and 40 watts for a typical LCD screen); and three to four watts when ‘asleep’. Up to 10% of a modern office’s electricity demand might be due to PCs and monitors.[1]

While some PCs allow low power settings, there are many situations, especially in a networked environment, where processes running on the computer will prevent the low power settings from taking effect. This can have a dramatic effect on energy use that is invisible to the user. The monitor may have gone into standby mode, and the PC may appear to be idle, but operational testing has shown that on any given day an average of over 50% of an organisation's computers would fail to go to sleep, and over time this happened to over 90% of the machines.[1]

Windows 'Insomnia' (Sleepless PCs)

The Windows power management system is based upon an idle timer. If the computer is idle for longer than the preset timeout then the PC may be configured to sleep or hibernate. The user may configure the timeout using the Control Panel. Windows uses a combination of user activity and CPU activity to determine when the computer is idle.

Applications can temporarily inhibit this timer by using the SetThreadExecutionState API.[2] There are legitimate reasons why this may be necessary such as burning a DVD or playing a video. However, in many cases applications can unnecessarily prevent power management from working. This is commonly known as Windows 'Insomnia' and can be a significant barrier to successfully implementing power management.

Common causes of 'insomnia' include:

  • Legacy or non-power management aware applications
  • Open file handles on remote computers
  • Faulty mice which can cause pointer drift. This makes the operating system believe that a user is present
  • Scheduled maintenance tasks causing significant CPU activity
  • High network activity

Software solutions

Operating systems have built-in settings to control power use. Microsoft Windows supports predefined power plans and custom sleep and hibernation settings through a Control Panel Power Options applet.[3] Apple's OS X includes idle and sleep configuration settings through the Energy Saver System Preferences applet.[4] Likewise, Linux distributions include a variety of power management settings and tools.[5]

There is a significant market in third-party PC power management software offering features beyond those present in the Windows operating system.[6][7][8] Products are targeted at enterprise environments offering Active Directory integration and per-user/per-machine settings with the more advanced offering multiple power plans, scheduled power plans, anti-insomnia features and enterprise power usage reporting. Notable vendors include 1E NightWatchman,[9][10] Data Synergy PowerMAN (Software),[11] Faronics Power Save,[12][13] Verdiem SURVEYOR.[14] and EnviProt Auto Shutdown Manager[15]

Using this type of energy management tool on an organisation's network has been demonstrated to save on average 200 kg of CO2 emissions per PC per year, and generate $36 per PC per year in energy savings.[16] An organisation such as a large office, with 4,000 employees, would be able to make CO2 emissions savings of over 800 tonnes and about $140,000 per year in energy savings. A large corporation with 50,000 employees could save 10,000 tonnes of CO2 and about $1.7 million per year in energy costs.[17]

UK Carbon Reduction Commitment incentives

With the Carbon Reduction Commitment (CRC) regulations coming into force in 2010, many businesses will be required to "budget" for their emissions of Carbon Dioxide. Organisations will be required to buy allowances to cover their CO2 emissions; top performers will receive financial rewards; and poor performers will be penalized.

The CRC uses electricity consumption as a means for determining which organizations fall under the new regulations, and covers all organizations with an electricity consumption of greater than 6,000 MWh per year (equivalent to emissions of approximately 1,280 tonnes CO2 per year from electricity use). Organizations must purchase allowances to cover all of their CO2 emissions with the exception of transport.[18] The CRC will incentivise energy efficiency and greenhouse gas emissions reduction in the non-energy intensive sector of business and industry.

As well as driving supply side measures to reduce the carbon intensity of energy consumed, the CRC will also provide big incentives for demand side energy efficiency. Once quick wins have been identified, attention will become more and more focused on harder to reach energy losses. These include energy losses distributed across organizations due to the organizations physical infrastructure, and also the way it uses energy consuming devices.

By looking at IT operations and energy use, proven energy management tools demonstrate that the CRC target of 4 million tonnes of CO2 emissions reduced by 2020 is readily achievable.

See also

References

  1. 1.0 1.1 Sleepless of Seattle; Why Windows Power Management Doesn't Always Work, Mark Blackburn, Strategy Analyst, 1E, January 2009.
  2. Lua error in package.lua at line 80: module 'strict' not found.
  3. Lua error in package.lua at line 80: module 'strict' not found.
  4. Lua error in package.lua at line 80: module 'strict' not found.
  5. Lua error in package.lua at line 80: module 'strict' not found.
  6. Lua error in package.lua at line 80: module 'strict' not found.
  7. Lua error in package.lua at line 80: module 'strict' not found.
  8. Lua error in package.lua at line 80: module 'strict' not found.
  9. Lua error in package.lua at line 80: module 'strict' not found.
  10. Lua error in package.lua at line 80: module 'strict' not found.
  11. Lua error in package.lua at line 80: module 'strict' not found.
  12. Lua error in package.lua at line 80: module 'strict' not found.
  13. Lua error in package.lua at line 80: module 'strict' not found.
  14. Lua error in package.lua at line 80: module 'strict' not found.
  15. Lua error in package.lua at line 80: module 'strict' not found.
  16. Lua error in package.lua at line 80: module 'strict' not found.
  17. Lua error in package.lua at line 80: module 'strict' not found.
  18. http://www.decc.gov.uk/en/content/cms/what_we_do/lc_uk/crc/crc.aspx