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-30.01:38:36
SpamBayes Score 0.00031022518
Marked as misclassified No
Message-id <1327887520.15.0.329658528191.issue13845@psf.upfronthosting.co.za>
In-reply-to
Content
Two articles (Microsoft and IBM) about high resolution time on Windows:
http://msdn.microsoft.com/en-us/magazine/cc163996.aspx
http://www.ibm.com/developerworks/library/i-seconds/

I installed the Windows port of the NTP daemon:
http://www.meinberg.de/english/sw/ntp.htm

Using the NTP daemon, the resolution is 1 ms instead of 15 ms (on Windows Seven). It looks like it is possible to have a resolution of 0.5 ms, but I failed to get this resolution.

Attached patch is much more simple than the previous one: it only changes _PyTime_gettimeofday().
History
Date User Action Args
2012-01-30 01:38:40vstinnersetrecipients: + vstinner, amaury.forgeotdarc, belopolsky, rosslagerwall
2012-01-30 01:38:40vstinnersetmessageid: <1327887520.15.0.329658528191.issue13845@psf.upfronthosting.co.za>
2012-01-30 01:38:39vstinnerlinkissue13845 messages
2012-01-30 01:38:38vstinnercreate