➜

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 nirai
Recipients DazWorrall, aconrad, alex, andrix, brian.curtin, carljm, coderanger, cool-RR, dabeaz, djc, donaldjeo, durin42, eric.araujo, eric.smith, flox, gregory.p.smith, jcea, jhylton, karld, kevinwatters, konryd, larry, loewis, mahmoudimus, movement, neologix, nirai, pitrou, rcohen, rh0dium, tarek, thouis, ysj.ray
Date 2010-04-28.19:17:43
SpamBayes Score 0.15288442
Marked as misclassified No
Message-id <1272482265.48.0.291749923851.issue7946@psf.upfronthosting.co.za>
In-reply-to
Content 
On Wed, Apr 28, 2010 at 12:41 AM, Larry Hastings wrote:

> The simple solution: give up QPC and use timeGetTime() with timeBeginPeriod(1), which is totally 
> reliable but only has millisecond accuracy at best.

It is preferable to use a high precision clock and I think the code addresses the multi-core time skew problem (pending testing).
History
Date User Action Args
2010-04-28 19:17:46niraisetrecipients: + nirai, loewis, jhylton, gregory.p.smith, jcea, pitrou, movement, larry, eric.smith, kevinwatters, tarek, djc, karld, carljm, coderanger, durin42, eric.araujo, alex, andrix, konryd, brian.curtin, flox, DazWorrall, cool-RR, rh0dium, rcohen, dabeaz, mahmoudimus, aconrad, ysj.ray, neologix, thouis, donaldjeo
2010-04-28 19:17:45niraisetmessageid: <1272482265.48.0.291749923851.issue7946@psf.upfronthosting.co.za>
2010-04-28 19:17:43nirailinkissue7946 messages
2010-04-28 19:17:43niraicreate