gh-88494: Use QueryPerformanceCounter() for time.monotonic() by vstinner · Pull Request #116781 · python/cpython

vstinner

On Windows, time.monotonic() now uses the QueryPerformanceCounter()
clock to have a resolution better than 1 us, instead of the
gGetTickCount64() clock which has a resolution of 15.6 ms.

vstinner added a commit to vstinner/cpython that referenced this pull request

Mar 20, 2024

…ython#116781)

On Windows, time.monotonic() now uses the QueryPerformanceCounter()
clock to have a resolution better than 1 us, instead of the
gGetTickCount64() clock which has a resolution of 15.6 ms.

adorilson pushed a commit to adorilson/cpython that referenced this pull request

Mar 25, 2024

…ython#116781)

On Windows, time.monotonic() now uses the QueryPerformanceCounter()
clock to have a resolution better than 1 us, instead of the
gGetTickCount64() clock which has a resolution of 15.6 ms.

diegorusso pushed a commit to diegorusso/cpython that referenced this pull request

Apr 17, 2024

…ython#116781)

On Windows, time.monotonic() now uses the QueryPerformanceCounter()
clock to have a resolution better than 1 us, instead of the
gGetTickCount64() clock which has a resolution of 15.6 ms.

vstinner added a commit to vstinner/distributed that referenced this pull request

May 7, 2024

Closes dask#8641.

_WindowsTime is no longer needed on Windows with Python 3.13. On
Windows, Python 3.13 now uses GetSystemTimePreciseAsFileTime() for
time.time() and QueryPerformanceCounter() for time.monotonic().

* python/cpython#116781
* python/cpython#116822

fjetter pushed a commit to dask/distributed that referenced this pull request

May 8, 2024

Closes #8641.

_WindowsTime is no longer needed on Windows with Python 3.13. On
Windows, Python 3.13 now uses GetSystemTimePreciseAsFileTime() for
time.time() and QueryPerformanceCounter() for time.monotonic().

* python/cpython#116781
* python/cpython#116822