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 kristjan.jonsson
Recipients anacrolix, belopolsky, brian.curtin, eric.araujo, glenn, kristjan.jonsson, michael.foord, pitrou, vstinner
Date 2011-08-30.11:49:03
SpamBayes Score 0.0052854987
Marked as misclassified No
Message-id <1314704944.44.0.617943265663.issue10278@psf.upfronthosting.co.za>
In-reply-to
Content
The problem with QueryPerformanceCounter is that it drifts.  It has high resolution, but can drift far out of sync with GetTickCount64.
The best solutions on windows combine the two, but that's tricky to impolement.

QPC will wrap, but only after a long time.  its 64 bits, and with a frequency of 1GHz, that takes some 600 years.
Of course, with 10GHz we're down to 60 years, but by that time, we will have python 2.8
History
Date User Action Args
2011-08-30 11:49:04kristjan.jonssonsetrecipients: + kristjan.jonsson, belopolsky, pitrou, vstinner, eric.araujo, michael.foord, brian.curtin, glenn, anacrolix
2011-08-30 11:49:04kristjan.jonssonsetmessageid: <1314704944.44.0.617943265663.issue10278@psf.upfronthosting.co.za>
2011-08-30 11:49:03kristjan.jonssonlinkissue10278 messages
2011-08-30 11:49:03kristjan.jonssoncreate