Differences between revisions 24 and 25
Revision 24 as of 2008-11-13 19:06:53
Size: 3141
Editor: HowardNoble
Comment:
Revision 25 as of 2008-11-13 21:11:02
Size: 3441
Editor: HowardNoble
Comment:
Deletions are marked like this. Additions are marked like this.
Line 5: Line 5:
A single desktop computer will consume approximately £75 of electricity per year if they are left on all the time. If they are put in a low power state when not in use this cost is likely to fall to £15 for the majority of users (insert ref.).This figure extrapolated to all the estimated 720 000 computers in UK Universities equates to an annual saving of around £40 million. This calculation assumes that all these computers can be switched off at the end of each normal working day which will not be the case. Computers are often left on for the following reasons: A single desktop computer will consume approximately £75 of electricity per year if they are left on all the time. If they are put in a low power state when not in use this cost is likely to fall to £15 for the majority of users (insert ref.).This figure extrapolated to all the estimated 720 000 computers in UK Universities equates to an annual saving of around £40 million. There are a wide range of assumptions in these headline figures so each organisation is advised to gather information about computer usage patterns, computer power consumption and electricity prices.
Line 7: Line 7:
 * So that a central backup service can make a copy of files overnight
 * So that a central service can install general software updates and security patches
 * To allow access to a computer when off site e.g. to retrieve a file while at a conference
 * To avoid waiting for a computer to start up from off
 * So that a personal computer can also act as a web server or central file store
 * A personal computer is used to keep another computer on ("keep alives")
 * A computer is used to constantly filter emails so that email folders are organised when accessing messages through the web
 * To allow spare computing capacity to be used by computer modelling projects e.g. SETI, climateprediction.net and GRID experiments in general
 * Standby (S3) and hibernate (S4) power saving modes cannot be implemented reliably on many computers
Any organisation that wants to reduce the carbon footprint and financial cost associated with its desktop computing infrastructure will recognise at least some of the following problems:

 * Users need to leave their computer on for at least one day a week so that a central backup service can make a copy of files overnight
 * Computers are left on all the time in case there is the need to install software updates or security patches
 * Users leave their computer of all the time so that they can use it remotely to for instance retrieve a file while at a conference
 * Computers are left on so that people do not have to wait for it to start up or boot
 * Desktop computers are used as a web server or file store
 * Desktop computer is used to keep another computer on ("keep alives")
 * Computer is used to constantly filter emails so that email folders are organised when accessing an inbox via the web
 * Spare computing capacity is used by computer modelling projects e.g. SETI, climateprediction.net and GRID experiments in general
 * Standby (S3) and hibernate (S4) power saving modes cannot be implemented reliably

This page is under construction!

A single desktop computer will consume approximately £75 of electricity per year if they are left on all the time. If they are put in a low power state when not in use this cost is likely to fall to £15 for the majority of users (insert ref.).This figure extrapolated to all the estimated 720 000 computers in UK Universities equates to an annual saving of around £40 million. There are a wide range of assumptions in these headline figures so each organisation is advised to gather information about computer usage patterns, computer power consumption and electricity prices.

Any organisation that wants to reduce the carbon footprint and financial cost associated with its desktop computing infrastructure will recognise at least some of the following problems:

  • Users need to leave their computer on for at least one day a week so that a central backup service can make a copy of files overnight
  • Computers are left on all the time in case there is the need to install software updates or security patches
  • Users leave their computer of all the time so that they can use it remotely to for instance retrieve a file while at a conference
  • Computers are left on so that people do not have to wait for it to start up or boot
  • Desktop computers are used as a web server or file store
  • Desktop computer is used to keep another computer on ("keep alives")
  • Computer is used to constantly filter emails so that email folders are organised when accessing an inbox via the web
  • Spare computing capacity is used by computer modelling projects e.g. SETI, climateprediction.net and GRID experiments in general
  • Standby (S3) and hibernate (S4) power saving modes cannot be implemented reliably

Many of these reasons mean that computers are being left on 'just in case' they are needed which means inevitably that there is likely to be extensive periods of time that computers are consuming electricity without doing useful work. Tools can be provided for IT managers and end-users that support the objective of minimising this wasted energy but organisations will also have to make decisions on whether practices need to change to save CO2 emissions and money.

TableOfContents([2])

Tools and techniques

Enabling users to wake computers up remotely

It is possible to provide the ability for IT managers and end-users to wake computers that they own using another computer. By providing a facility to turn computers on remotely, it becomes possible to ask people to turn their computers to low power states more often. For instance, many organisations will ask their staff to leave their computers on so that the a backup service can access the hard drive and create a copy of files. If computers can be woken up by the backup service then users can switch them off without disrupting this essential activity. This same logic applies to other services that may need access to a computer more regularly e.g. services that install software updates, anti-virus checking and so on.

Case study: University of Oxford

The University of Oxford developed a wake-on-LAN infrastructure that enables IT officers, end-users and 3rd party software to wake computers remotely. ["lcict:wol"]

Configuring computers to move into low power states automatically