It turns out that Google’s Chrome browser has been telling that other OS not to save power by napping, for years.“Instead of waking up the processor every 15.625ms, Chrome tells Windows to have it wake up every 1.000ms. So while your PC normally wakes up the processor 64 times per second when it’s idle, as long as you have Chrome running, the processor wakes up 1,000 times per second.
Chrome doesn’t have to be running in the foreground to have this effect, either. There’s only one platform timer, so when one application changes its resolution, the new value becomes a system-wide setting.” This has been a huge drain on the batteries of notebooks.
Now, some claim this is a bug in Chrome, but it’s not. It’s a bug in that other OS that lets a user-space application mess with a system-wide setting. This is yet another example of a single-user OS designed in the 1980s still being fragile decades later. This is yet another example of M$ making an OS with too many vulnerable edges for malware to interfere with our use of the hardware we own. This is another example of what happens when you let salesmen design an OS.
I recommend Debian GNU/Linux. It’s a real OS that works for you, not some distant team of salesmen. In GNU/Linux, introduction of the “tickless” kernel and other such features combine to give serious reduction in notebooks’ drain. Intel wrote a whitepaper which shows many watts saved for notebooks and servers by tickless idle and several other measures. Of course, an application could set up interrupts to defeat that but it’s not a system-wide problem. The operating system responds automatically and does not take a new setting from one errant application.