Differences between revisions 9 and 11 (spanning 2 versions)
Revision 9 as of 2008-11-11 11:23:31
Size: 2131
Editor: HowardNoble
Comment:
Revision 11 as of 2008-11-11 17:13:17
Size: 2252
Editor: HowardNoble
Comment:
Deletions are marked like this. Additions are marked like this.
Line 2: Line 2:
 The aim of this section of the Low Carbon ICT wiki is to provide information that helps IT managers and end-users to minimise the electricity consumption by PCs and laptops when they are not doing useful work. Desktop computers are left on to: Desktop computers are often left on all the time. The main reasons for this practice are:
Line 4: Line 4:
 1. Allow ICT manager to install software patches
 1. Save the time required to start up a computer from off
 * An external service needs access the computer e.g. backup
 * An individual needs to access their computer e.g. to retrieve a file while at a conference
 * An individual wants to avoid waiting for a computer to start up
As a result computers are often on, consuming electricity without doing any useful work. Unfortunately moving computers into low power states is more difficult than switching off a light bulb - something that most people are accustomed to. This section of the low carbon ICT wiki aims to provide information about tools that can be deployed to support organisations in reducing the costs and carbon footprint of their desktop computing infrastructure.[[TableOfContents([2])]]
Line 7: Line 9:
 1. Allow remote backup services to access computers
 1. Allow end-users to have remote access to their computer (e.g. to retrieve files)
 1. To run email filtering processes
 1. To run 'keep-alive' processes e.g. using SSH clients
Unfortunately, since these events are typically short-lived, keeping computers on for these reasons means that they are still likely to consume large amounts of electricity without doing useful work.
It is possible to provide a tools to for end-users and ICT managers to reduce this wasted energy. However, the provision of new tools will need to be accompanied by people adopting more energy efficient ways of working.[[TableOfContents([2])]]
Line 14: Line 10:
= Overview =
Line 16: Line 12:
= Support =
== Local power management ==

== Automatic power management ==
Most desktop computers can be configured to move into low power states after a defined period of inactivity. Most operating systems can move a computer in S3 (often called "sleep" or "standby" ) or S4 ("hibernate"). Unfortunately computers may move into low power state when a process is running
 1. Once in a low power state computers may not respond to being turned on remotely
Line 23: Line 21:
=== Enable end-users to configure power management ===
===
Distribute power management setting centrally ===
 * Enable end-users to configure power management
* Distribute power management setting centrally
Line 34: Line 32:
= Support =
Line 36: Line 35:

Desktop computers are often left on all the time. The main reasons for this practice are:

  • An external service needs access the computer e.g. backup
  • An individual needs to access their computer e.g. to retrieve a file while at a conference
  • An individual wants to avoid waiting for a computer to start up

As a result computers are often on, consuming electricity without doing any useful work. Unfortunately moving computers into low power states is more difficult than switching off a light bulb - something that most people are accustomed to. This section of the low carbon ICT wiki aims to provide information about tools that can be deployed to support organisations in reducing the costs and carbon footprint of their desktop computing infrastructure.TableOfContents([2])

Tools and techniques

Automatic power management

Most desktop computers can be configured to move into low power states after a defined period of inactivity. Most operating systems can move a computer in S3 (often called "sleep" or "standby" ) or S4 ("hibernate"). Unfortunately computers may move into low power state when a process is running

  1. Once in a low power state computers may not respond to being turned on remotely
  2. Automatically putting a computer into S3, S4 or S5 power states
  3. Issues
    • when in standby computers cannot easily be switched off automatically
    • computers don't wake from S3 or S4 reliably
    • don't want to interrupt services that may be running in background
  4. Enable end-users to configure power management
  5. Distribute power management setting centrally

Remote power management

Switching computers on remotely

Wake-on-LAN

  • Introductory text
  • ["lcict:wol"]

VPro

Switching computers off remotely

  1. How to turn computer off remotely

Support

More efficient working practices

create matrix of: (1) practice/ activity description (2) measure of how much energy will be saved (3) who the practice is relevant to * switching monitor off will prevent it turning on when accessing computer remotely

  • implement power management