Processor Throttling In Windows XP
TomSlick writes "Michael Chu, a former Intel employee, has written up a fairly interesting and readable summary of Windows XP power schemes as they relate to Intel processor throttling. An old topic, but one still relevant as many business notebooks still use XP."
If you run XP, set the power scheme to "Minimal Power Management".
Unless, as a twitch-gamer, you (think you) can't afford to lose even a single CPU cycle, then by all means continue trying to heat your house in "Always On" mode (or the default of "Home/Office Desk", which means the same thing to AC-powered non-laptops).
As an interesting aside, TFA's author recommends "Portable/Laptop" mode; However, he writes that coming from the Intel world. Users of AMD chips (myself included) have noticed problems with CnQ (AMD's version of SpeedStep) not working correctly unless you set it to "Minimal Power Management", which according to the charts in the linked article, should work the same as "Portable/Laptop".
What is so wrong with Vista on modern hardware?
Well, instead of requiring a dual-core CPU and 2+GB to run tolerably, you could use that second core and second gig to actually run things you want, rather than nothing but OS-related eye-candy and DRM crapware.
Now, if you have a nostalgic desire for a machine that "feels" just like XP on a PII-300 with 256MB, by all means run Vista. If, however, you consider the OS "just a way to get to the real programs", you may want to consider upgrading from Vista to XP.
There is a program called cpufreq-selector that should come with the default installation. There is even a Gnome panel applet that interacts with it called CPU Frequency Scaling Monitor.
Sure you can:
cpudyn - CPU dynamic frequency control for processors with scaling
cpufreqd - fully configurable daemon for dynamic frequency and voltage scaling
cpufrequtils - utilities to deal with the cpufreq Linux kernel feature
All are found in your apt repository.
"CPU(s) begin in lowest performance state and then get slower and slower"
This is remarkably sloppy writing for a supposedly technical article. Is there a performance state even lower than the lowest? Is he talking about clock modulation? Does it get "slower and slower" but never faster and faster?
Maybe I'll give it another shot when the service pack comes out.
The soylentnews experiment has been a dismal failure.