In the end, I took this as a discussion of thermal energy dissipation as it pertains to mobile devices. In other words, battery life. My conclusion is that we need to vastly improve the energy density of batteries (or consider using carbon-based energy sources to power mobile devices). Edit: Not sure why this is getting downvoted. The end of the article really does discuss mobile devices and energy dissipation - whic…
The batteries in your devices represent decades of R&D; scientists are spending entire careers looking for 5% improvements. Saying "just use better batteries" appears to trivialize that effort. Also, programmers (generally) aren't qualified to invent new battery chemistries, but they can make software use fewer cycles.
Optimizing for Fan Noise
11–20 of 30 posts
Re: Optimizing for Fan Noise
#12Doubling the speed of a program by moving from one to four cores is a win if you're looking at the raw benchmark numbers, but an overall loss in terms of computation per watt. The first time I read this I didn't understand it, but the author has laid a trap here for the unwary reader in the word "doubling". If you can get 4x the performance using 4 cores the energy efficiency is the same or better, but if your progra…
Basically, you will never get a linear increase with parallel computing, especially on consumer type apps that are much more synchronous. So running multiple cores, with requisite context switches will get less computing per watt, even if it isn't as bad as the 2x number.
Re: Optimizing for Fan Noise
#13Re: Optimizing for Fan Noise
#14Doubling the speed of a program by moving from one to four cores is a win if you're looking at the raw benchmark numbers, but an overall loss in terms of computation per watt. The first time I read this I didn't understand it, but the author has laid a trap here for the unwary reader in the word "doubling". If you can get 4x the performance using 4 cores the energy efficiency is the same or better, but if your progra…
http://en.wikipedia.org/wiki/Parallel_computing#Amdahl.27s_l... Basically, you will never get a linear increase with parallel computing, especially on consumer type apps that are much more synchronous. So running multiple cores, with requisite context switches will get less computing per watt, even if it isn't as bad as the 2x number.
Can you explain this part?
Re: Optimizing for Fan Noise
#15Doubling the speed of a program by moving from one to four cores is a win if you're looking at the raw benchmark numbers, but an overall loss in terms of computation per watt. The first time I read this I didn't understand it, but the author has laid a trap here for the unwary reader in the word "doubling". If you can get 4x the performance using 4 cores the energy efficiency is the same or better, but if your progra…
http://en.wikipedia.org/wiki/Parallel_computing#Amdahl.27s_l... Basically, you will never get a linear increase with parallel computing, especially on consumer type apps that are much more synchronous. So running multiple cores, with requisite context switches will get less computing per watt, even if it isn't as bad as the 2x number.
Re: Optimizing for Fan Noise
#16The author makes a point that moving an application from one core to four might look good in benchmarks, but that it will peg all four cores and cause the fan to start running. I'd argue that that is precisely what you want, and that the operating system should provide a user-controlled mechanism to throttle the CPU back. That way, if you want raw performance, you can get it, but if you want a quiet computer and long…
Windows offers pretty good configuration options for power management, including setting maximum processor speed (as a percentage) while running on battery or on AC.
The author seems to be blurring the lines between fixed tasks like transcoding videos and interactive tasks like games. It's not at all obvious that transcoding with a single-threaded app saves any power over the duration of the job than with a multi-threaded implementation. Most laptop CPUs don't have the kind of power gating that are on the latest chips like the Core i7, so even if no instructions are issued to a core, it still draws some power.
With interactive tasks, the only way to save power is to do less, so that the CPU and other components can spend most of their time waiting for the user while in a low-power state. Predictive caching and speculative execution increase the responsiveness of a system on average, but at the cost of performing some tasks whose results won't be used. The only real take-away from this article is that apps that might be used on the go should provide a way to disable these techniques.
(It's important to note that games don't do a lot of this stuff, so there your only options are to turn down the eye candy and the frame rate. A good example of how to accomplish this is Torchlight's netbook mode.)
Re: Optimizing for Fan Noise
#17Re: Optimizing for Fan Noise
#18Use a CPU that does not require a fan. The 1 Mhz 6502 did not need a fan. The ARM, Apple A4, and others processors do not need fans. The problem is the Intel architecture has too many fans.
Re: Optimizing for Fan Noise
#19In addition to this, the computer is on the floor, not right next to my ears. So even if it were louder, it would still not annoy me.
So basically, I think your computer is broken if you can hear the fans. It's either designed wrong, or in the wrong position, or both.