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, alex, brian.curtin, carljm, coderanger, dabeaz, eric.smith, flox, jcea, jhylton, karld, kevinwatters, loewis, mahmoudimus, nirai, pitrou, rcohen, rh0dium, tarek
Date 2010-03-25.17:58:04
SpamBayes Score 9.410749e-05
Marked as misclassified No
Message-id <1269539886.34.0.951160418724.issue7946@psf.upfronthosting.co.za>
In-reply-to
Content
Well, on initial check the scheduler seems to work well with regular gettimeofday() wall clock instead of clock_gettime().

:)

/* Return thread running time in seconds (with nsec precision). */
static inline long double get_thread_timestamp(void) {
    return get_timestamp(); // wall clock via gettimeofday()
    /*struct timespec ts;
    clock_gettime(CLOCK_THREAD_CPUTIME_ID, &ts);
    return (long double) ts.tv_sec + ts.tv_nsec * 0.000000001;*/
}

Does it make things better on your system?
History
Date User Action Args
2010-03-25 17:58:06niraisetrecipients: + nirai, loewis, jhylton, jcea, pitrou, eric.smith, kevinwatters, tarek, karld, carljm, coderanger, alex, brian.curtin, flox, DazWorrall, rh0dium, rcohen, dabeaz, mahmoudimus
2010-03-25 17:58:06niraisetmessageid: <1269539886.34.0.951160418724.issue7946@psf.upfronthosting.co.za>
2010-03-25 17:58:04nirailinkissue7946 messages
2010-03-25 17:58:04niraicreate