Hacker News new | ask | show | jobs
by BitterAmethyst 2087 days ago
At work we have an application that calls `timeBeginPeriod(1)` to get timer callbacks (from `CreateTimerQueue`) firing at 5ms resolutions but we are not seeing the behaviour described in the article. We observe no change to the timer resolution after calling `timeBeginPeriod(1)`, which unfortunatly is a breaking change to our app.

The lack of information and response from Microsoft on this has been quite frustrating.
1 comments
vardump 2087 days ago
Yeah, I just came to the same conclusion.

Win10 2004 timer changes are breaking.

Timer frequency adjustments (timeBeginPeriod) don't seem to affect Windows timers in the same process like they used to do!

Again. In Win10 2004, if you do timeBeginPeriod(1), timers in the same process (other than using the deprecated multimedia timer) seem to only trigger every 15-16 ms or so instead of 1 ms.

This is bad.

As a sidenote about Win10 2004, after timeBeginPeriod(1), Sleep(1) seems to take about 2 ms per call. Or at least it seems to take about 1950 ms to call Sleep(1) 1000 times when I tested it. Confusing.

link
BitterAmethyst 2087 days ago
Yeah.

There is an a ticket opened in the `Feedback Hub` app for it that I've been checking but there seems to be no acknowledgement from Microsoft about this, which is one of the more annoying aspects.

link