Re:Windows Timer Resolution: The Great Rule Change
by mehrdadn on Monday October 05, 2020 @06:42AM
(#24686402)
Might be due to my use of APCs rather than waiting on the object. Not bothered enough to try it myself but I guess you can try WaitForSingleObject on the timer to see if it behaves similarly...
[ Parent
| on HN ]
Re:Windows Timer Resolution: The Great Rule Change
by vardump on Monday October 05, 2020 @06:48AM
(#24686427)
On 2004, I tried timeBeginPeriod(1) and calling Sleep(1) 1000 times. Perplexingly it took a bit under 2 seconds.
On 1809 same took about 1.3 seconds.
I'm at loss... Windows timers have yet again managed to do really weird, unexpected things.
I really hope this mess doesn't affect device drivers, or there could be a world of hurt coming up.
Re:Windows Timer Resolution: The Great Rule Change
by mehrdadn on Monday October 05, 2020 @06:54AM
(#24686457)
I think it's due to my use of APCs like I said. Try replacing SleepEx(100, TRUE) with WaitForSingleObject(handle, INFINITE).
Edit: Never mind. Seems it might not be the APCs. Maybe some callee of Sleep(Ex) is just rounding up the wait interval to a time slice somewhere. Not sure... would need some digging.