The energy consumption of modern CPUs varies significantly depending on the task that is currently executing - however, I have not seen any study done to relate this to these popular distributed computing projects.
The energy consumption of a 1000MHz Athlon PC[1] was tested under both low and high load[2] conditions. At low load the PC consumed 92 W, with the monitor consuming an additional 82 W. With the UD 'think' project running, power consumption of the PC rose to 124 W (a rise of 32 W or 35%).
Cost implications: If such a PC is used in an office environment (8 hrs per day - light CPU load), energy consumption would be expected to be 1.4 kWh per day, an approximate cost of $0.14[2]. Running a distributed project would increase this to 1.6 kWh/d ($0.16). Per year[3] these figures become 360 ($36) and 430 kWh ($43).
In a situation where such a PC operates 24/7, these figures become 1520 kWH ($152) and 1800 kWH ($180). [Edit] Note that the individual figures are of debateable meaning as they assume that the monitor operates continuously. Excluding monitor these figures are 806 kWh ($81) and 1086 kWH ($109) - a cost of $28 per year. [/Edit - thanks to Bakwetu]
Further research: effects of different OS idle systems (use of HLT command), effects of different types of CPU, effect of different types of program including power consumption from 3d accelerators, viability of 'undervolting' a CPU to bring cost savings
[1] - PC specification: Athlon Thunderbird 1000 MHz, Abit KT7-RAID, Quantum 5400 rpm HD, 256 MB PC 133 SDRAM, Enermax 430W PSU; OS Windows ME.
[2] - Low load consisted of running a popular word processor and typing at a rate of approx 40 wpm. Spelling and grammar checking were enabled. High load involved running a distributed processing task that consumed 100% of CPU time.
[3] - At a unit cost of $0.10 per kWH
[4] - 5 working days per week.
The energy consumption of a 1000MHz Athlon PC[1] was tested under both low and high load[2] conditions. At low load the PC consumed 92 W, with the monitor consuming an additional 82 W. With the UD 'think' project running, power consumption of the PC rose to 124 W (a rise of 32 W or 35%).
Cost implications: If such a PC is used in an office environment (8 hrs per day - light CPU load), energy consumption would be expected to be 1.4 kWh per day, an approximate cost of $0.14[2]. Running a distributed project would increase this to 1.6 kWh/d ($0.16). Per year[3] these figures become 360 ($36) and 430 kWh ($43).
In a situation where such a PC operates 24/7, these figures become 1520 kWH ($152) and 1800 kWH ($180). [Edit] Note that the individual figures are of debateable meaning as they assume that the monitor operates continuously. Excluding monitor these figures are 806 kWh ($81) and 1086 kWH ($109) - a cost of $28 per year. [/Edit - thanks to Bakwetu]
Further research: effects of different OS idle systems (use of HLT command), effects of different types of CPU, effect of different types of program including power consumption from 3d accelerators, viability of 'undervolting' a CPU to bring cost savings
[1] - PC specification: Athlon Thunderbird 1000 MHz, Abit KT7-RAID, Quantum 5400 rpm HD, 256 MB PC 133 SDRAM, Enermax 430W PSU; OS Windows ME.
[2] - Low load consisted of running a popular word processor and typing at a rate of approx 40 wpm. Spelling and grammar checking were enabled. High load involved running a distributed processing task that consumed 100% of CPU time.
[3] - At a unit cost of $0.10 per kWH
[4] - 5 working days per week.