Linked by Thom Holwerda on Wed 10th Jul 2013 11:23 UTC
Windows "The default timer resolution on Windows is 15.6 ms - a timer interrupt 64 times a second. When programs increase the timer frequency they increase power consumption and harm battery life. They also waste more compute power than I would ever have expected " they make your computer run slower! Because of these problems Microsoft has been telling developers to not increase the timer frequency for years. So how come almost every time I notice that my timer frequency has been raised it's been done by a Microsoft program?" Fascinating article.
Thread beginning with comment 566711
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE: Other OSes?
by UltraZelda64 on Wed 10th Jul 2013 19:28 UTC in reply to "Other OSes?"
Member since:

What do you mean by "fully tickless?" Just wondering, because I thought that Linux--speaking specifically of the kernel--was fully tickless (or at least comes with the option). Are you referring to "Linux" in the distribution sense, as in the userland and all the other tools and programs running on top of it?

Back when the "tickless" setting was introduced into the kernel (quite a while ago) I remember reading that a lot of packages had to be updated to take advantage of it. I'm guessing that's what you're referring to? Either way, it's been a long time... I figured by now virtually everything that needed updating should be updated by now. What could be left?

Reply Parent Score: 2

RE[2]: Other OSes?
by UltraZelda64 on Wed 10th Jul 2013 19:53 in reply to "RE: Other OSes?"
UltraZelda64 Member since:

Ah, out of curiosity I just stumbled upon this link in a Google search:

So, that was the first step, allowing an kernel to go into a tickless mode whenever it is idle. And now they are making further progress in making it tickless all the time. I think I understand now.

Edited 2013-07-10 19:56 UTC

Reply Parent Score: 4