Yes, computers are stupid, as MidiMagic proves. He's completely right, but the computers don't know that, so they turn the fan on when they shouldn't. We need to teach the computers that they should not generate additional heat when they are actually working rather than sitting idle. They need to follow MidiMagic's rules. He's obviously studied the phenomena.

I'll call Intel later today.

You are using the hard disk drive more. That does produce more heat.

Also, you probably notice the fan more when you are waiting for something to finish, than when you are busy doing something thought-intensive.

In every machine I have ever used, the fan either runs on high all the time, or cycles between high and low on a periodic basis, depending on the heat produced. During exams, when everyone has to be quiet, I hear the various computers cycling between high and low fan in a seemingly random pattern. If starting the exam produced more heat, they should all go to high at about the same time.

There is one other possibility, and that is a smart program or hardware in some brands of computers is figuring out when the disk drive is about to be used more, and turning up the fan in anticipation.

Processors generate heat. It is a very simple concept, with the newer processors, they are more 'energy efficient' which means they *will* perform less work, and thus generate less heat when you are doing nothing on the computer.

Unless you are running one of the original Pentium series processors, you are wrong.

If you are going to argue, go read the Intel Whitepages on how their processors work, and come back.

The disk drive does produce heat, unfortunately CPU (and newer chasis fans) are not designed for the hard disk drive, and if you don't believe me, open up a server, the fans are pulling air from the front, running it over the CPU heat sinks and out the back. Most of the time they are tunneled through plastic, so the air ONLY hits the CPUs, and RAM.

http://www.2cpu.com/gallery/sm-5015-UR/5015M_UR

If you *really* don't believe me, I can sit next to a daniweb server (which doesn't use any disk usage at all), force the CPU to spike, and the fans will go from 1k RPM to 15k RPM instantly.

I had Experience with Firefox 2, It uses lot of bandwidth in background until when no site is opened...Switch to version 3 (Beta 1) and choose yourself what to load or what not to under Options.

[memory jog]I was recently fixin' up some memory issues with one of my FF installs are I ran across something like this. Originally I was trying to find and fix problematic extensions, but my main workaround on that setup was the Config.trim_on_minimize. FWIW

Firefox 3 beta doesn't have the CPU bug, but it has many others

OK, so how does the CPU know whether the program it is running is doing a lot of work, or is just sitting there going through some status-checking loops? Does Windows tell it when it is doing work? It can't find out by analyzing the program, because a hardworking program could look a lot like an idling program.

Next, how does whatever device determines how busy the computer will be know that in advance? It can't telll what the user is going to do.

How does the CPU save power? Does the clock speed change? Does a second processor of a dual processor shut down? Those are the only power-saving methods I can think of that don't destroy data.

The only articles I could find on the web say that some laptops slow the CPU clock to half speed when no windows are executing code. And I found a few companies using overclocking (running the CPU beyond spec speed) for short periods.

And compared to the amount of power an average house uses, reducing CPU consumption is mousemilking.

In a data center environment, CPUs that are energystar compliant are very important.

The Intel white papers on an Intel Core2Duo state that the processor runs at only 30C when idle, and 55C when fully utilized, computers are very complicated machines, which include several pieces of equipment that work together to perform very complicated tasks. The motherboard will tell the CPU when it is about to recieve data from the I/O devices and/or PCI Bus, which then allows it to start speeding up. At the same time, the motherboard can detect how much work the CPU is doing, and control the speed of the fans in the system.

Your CPU is responsible for almost 30% of your computers power consumption, so from 30% to 10% adds up when you are talking about 20-50,000 systems.


In a much smaller area, my computer room has 5PCs, if I let the PC's idle and not do any work, the room sits at 76F, if I max out the CPU's running benchmarks for 20 minutes, the room is at 82F. (Real life test, I just did it)

When there are no instructions to run, the CPU is stopped (with the appropriate CPU instruction) and waits for an interrupt. The kernel does this. Programs don't handle events by busy-waiting, as you surmise, or if they do, they spend some time sleeping to avoid overusing the CPU. (If you ever wrote a program that busy-waited, you would see your CPU use rise to almost 100% and see your temperature rise, too.)

That explains why read-modify-write scientific operations based on real world events don't work anymore.

Kill the environmentalists who thought this up. They killed off a whole branch of science.