-
-
Notifications
You must be signed in to change notification settings - Fork 32.2k
bpo-41299: fix 16ms jitter in Windows threading timeouts #26568
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
Thanks @lunixbochs for the PR, and @zooba for merging it 🌮🎉.. I'm working now to backport this PR to: 3.10, 3.9. |
Sorry @lunixbochs and @zooba, I had trouble checking out the |
… precision time source (pythonGH-26568) (cherry picked from commit 449e6f0) Co-authored-by: Ryan Hileman <[email protected]>
GH-26579 is a backport of this pull request to the 3.9 branch. |
Thanks @lunixbochs for the PR, and @zooba for merging it 🌮🎉.. I'm working now to backport this PR to: 3.10. |
GH-26580 is a backport of this pull request to the 3.10 branch. |
… precision time source (pythonGH-26568) (cherry picked from commit 449e6f0) Co-authored-by: Ryan Hileman <[email protected]>
… precision time source (GH-26568) (cherry picked from commit 449e6f0) Co-authored-by: Ryan Hileman <[email protected]>
… precision time source (GH-26568) (GH-26580) (cherry picked from commit 449e6f0) Co-authored-by: Ryan Hileman <[email protected]> Co-authored-by: Ryan Hileman <[email protected]>
GetTickCount64() is quantized to 16ms, which makes it unsuitable for measuring short timeouts.
QueryPerformanceCounter() has been guaranteed to work since Windows XP. It should only return an error if you pass in an unaligned pointer, which should only happen if your compiler doesn't align the stack.
https://bugs.python.org/issue41299