CPU Heat w/ Distributed.Net Client?
yamla asks: "I run a dual-Celeron machine (
ABIT BP6) and
primarily use Linux. I am concerned about heat and so I have added a second fan and used thermal paste. When I run the distributed.net client, the heat is CPU1:45C(113F), CPU2:49C(120F), SYS:55C(131F). Without this client running, my system is about ten degrees cooler at CPU1:34C(93F), CPU2:35C(95F), SYS:44C(111F). My question is simple. Should I stop running the distributed.net client or is this difference in heat nothing to be concerned about?" Wow! I've heard of hot software, but this might be too literal for comfort.
On a comparative level, I used to have both a p133 and a p150, both which burnt your finger if you dared to touch them after a cpu-intensive job, but which never had any issues.
About 55 C is a bit on the hot side. Your probably best off getting a better heat sink for both of your CPU's and maybe adding yet another fan. Personally I perfer keeping my CPU's down in the 30 to 40 C range to reduce termal stress. All my systems have good enough cooling that they run at no more then 40 C (room temp 25 C) except for my junk Cyrix (got it for free as it's unstable due to being badly overclocked once) that runs at about 45 C
Having your system 10 C cooler is not suprising at all. When you CPU is doing nothing Linux puts the CPU into a low-power mode. The second anything happens, such as a interupt, the CPU is instantly switched back on. In this low-power mode very little heat is produced, you can guess the results of that. :)
Personally I wouldn't worry for now and keep on using Distributed.net Intel processors have pretty good heat tolerence. However while some people say that since the maximum temperature is 80 C you shouldn't worry at all I disagree. If you're running your CPU at 80 C you are going to cause quite a lot of problems! That's like always running your car at the red line. It won't wreck your engine immediatly but over a period of time will cause a lot of problems.