Author eryksun
Recipients Dennis Sweeney, SD, eryksun, ned.deily, paul.moore, pitrou, steve.dower, tim.golden, zach.ware
Date 2021-03-01.20:54:27
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1614632067.65.0.104849522789.issue41299@roundup.psfhosted.org>
In-reply-to
Content
>So there is no advised way around this then.

Changing the implementation of EnterNonRecursiveMutex() to use WinAPI QueryInterruptTime() instead of GetTickCount64() would allow increasing the wait precision by setting the system timer resolution to the minimum supported period via timeBeginPeriod() [1]. It seems reasonable to at least support doing this.

That said, changing the system timer resolution shouldn't be encouraged since it affects the entire system and can increase power consumption. If you have results in 2.7 similar what's shown in msg373660, check clockres in a separate terminal to see the current timer interval [2].

---
[1] https://docs.microsoft.com/en-us/windows/win32/api/timeapi/nf-timeapi-timebeginperiod
[2] https://docs.microsoft.com/en-us/sysinternals/downloads/clockres
History
Date User Action Args
2021-03-01 20:54:27eryksunsetrecipients: + eryksun, paul.moore, pitrou, tim.golden, ned.deily, zach.ware, steve.dower, Dennis Sweeney, SD
2021-03-01 20:54:27eryksunsetmessageid: <1614632067.65.0.104849522789.issue41299@roundup.psfhosted.org>
2021-03-01 20:54:27eryksunlinkissue41299 messages
2021-03-01 20:54:27eryksuncreate