The UK Home Automation Archive

Archive Home
Group Home
Search Archive


Advanced Search

The UKHA-ARCHIVE IS CEASING OPERATIONS 31 DEC 2024


[Message Prev][Message Next][Thread Prev][Thread Next][Message Index][Thread Index]

RE: idle cycles: cpuidle, cancer, and seti, etc.


  • Subject: RE: idle cycles: cpuidle, cancer, and seti, etc.
  • From: "UKHA" <mailinglists@xxxxxxxxxxx>
  • Date: Sat, 17 Apr 2004 09:44:44 +0100

Running UnitedDevices/SETI client does used more electricity (I've been
meaning to check exactly how much with my Watt Meter for about 6 months
now), this stands to reason as the CPU gets hotter.

Whether it will shorten the lifespan depends on how hot you let it get.
While AMD processor (which I mostly use) have a max. operating temp of
90'C, running them above 50'C is considered bad for them. My server runs at
about 44'C under full load (UnitedDevices) 24/7 for about six months, the
previous server for over two years. It pumps out a fair bit of heat, my
study is noticeably warmer than the rest of the house.

Running the CPU at 44'C *may* shorten it's life as the idle temp. is about
32'C, but it's something like from 20-30 years to 15-20 years, but
realistically I don't suppose the server will be running that hardware for
more than a couple of years before it starts to struggle with the every
increasing pile of software that it runs and must be upgraded....

The CPUIdle programs DO work, then use the built in CPU HALT command, this
basically 'pauses' the CPU for a moment, as it's doing nothing it's using
v.little electricity, it cools down a fraction, repeated HALTs cool the CPU
down to the required temp, however the CPU isn't actually doing anything
while the HALT command is happening so you are slowing down the CPU. NT,
Win2K, XP and Linux all use this command for power/temperature management,
however a bigger heat sink/fan/ducting is better idea.


-----Original Message-----
From: s369180 [mailto:yahoo@xxxxxxx]
Sent: 17 April 2004 07:40
To: ukha_d@xxxxxxx
Subject: [ukha_d] idle cycles: cpuidle, cancer, and seti, etc.


Hello,

I remember the debate over the cancer and seti programs. I am sure
they are both noble causes and don't wish to open that can of worms.
I am sure that since many people run more than one networked pc, it
could be possible to run both programs over your network and benefit
both causes.

Other than the division they caused within the list, is there any
reason not to run something like this? It does seem silly the cpu
sitting there idle waiting for some HA command to appear. The only
downside I can think of is that presumably a busy cpu is hotter than
an idle one. Does the pc power consumption go up much running these
programs and is there much of a temperature rise risking shortening
the cpu life?

Do these programs like cpuidle work? I tried it with win98se but it
seemed to cause my system to crash. Am I right to think that NT and
2k have this built-in so do not need such programs?

Thanks



UK Home Automation Meet 2004 - BOOK NOW!
http://www.ukha2004.com

http://www.automatedhome.co.uk

Member Offers - http://www.freeranger.co.uk/ukha



UKHA_D Main Index | UKHA_D Thread Index | UKHA_D Home | Archives Home

Comments to the Webmaster are always welcomed, please use this contact form . Note that as this site is a mailing list archive, the Webmaster has no control over the contents of the messages. Comments about message content should be directed to the relevant mailing list.