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.03572855 |
| Marked as misclassified | No |
| Message-id | <CAMpsgwY2ds7cdT1GKoDM4ADNYpBwTGGyr88J0bLOWh_GTfaSdw@mail.gmail.com> |
| In-reply-to | <1327402137.35.0.336450658447.issue13845@psf.upfronthosting.co.za> |
| Content | |
|---|---|
> 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: http://undocumented.ntinternals.net/UserMode/Undocumented%20Functions/Time/NtSetTimerResolution.html There are applications using this undocumented function. For example: http://www.lucashale.com/timer-resolution/ See also the timeBeginPeriod() function: http://msdn.microsoft.com/en-us/library/ms713413%28VS.85%29.aspx The user may have a special hardware (and its driver) or a special softwared (ntpd?) with a better accuracy. |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2012年01月24日 11:22:54 | vstinner | set | recipients: + vstinner, amaury.forgeotdarc, belopolsky, rosslagerwall |
| 2012年01月24日 11:22:53 | vstinner | link | issue13845 messages |
| 2012年01月24日 11:22:53 | vstinner | create | |