This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author vstinner
Recipients amaury.forgeotdarc, belopolsky, rosslagerwall, vstinner
Date 2012-01-24.11:22:53
SpamBayes Score 0.0357286
Marked as misclassified No
Message-id <CAMpsgwY2ds7cdT1GKoDM4ADNYpBwTGGyr88J0bLOWh_GTfaSdw@mail.gmail.com>
In-reply-to <1327402137.35.0.336450658447.issue13845@psf.upfronthosting.co.za>
> GetSystemTimeAsFileTime() represent durations as multiple of 100ns, unfortunately its value is only updated every 15ms or so.  Precision is not accuracy...

It is possible to improve the accuracy of this clock using the
undocumented NtSetTimerResolution() function:

There are applications using this undocumented function. For example:

See also the timeBeginPeriod() function:

The user may have a special hardware (and its driver) or a special
softwared (ntpd?) with a better accuracy.
Date User Action Args
2012-01-24 11:22:54vstinnersetrecipients: + vstinner, amaury.forgeotdarc, belopolsky, rosslagerwall
2012-01-24 11:22:53vstinnerlinkissue13845 messages
2012-01-24 11:22:53vstinnercreate