[Python-Dev] Use QueryPerformanceCounter() for time.monotonic() and/or time.highres()? (original) (raw)
Glyph glyph at twistedmatrix.com
Sat Mar 31 04:28:26 CEST 2012
- Previous message: [Python-Dev] Use QueryPerformanceCounter() for time.monotonic() and/or time.highres()?
- Next message: [Python-Dev] [Python-checkins] cpython (3.2): Issue #14409: IDLE doesn't not execute commands from shell with default
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Mar 30, 2012, at 10:25 PM, Glyph wrote:
On Mar 30, 2012, at 10:17 PM, Victor Stinner wrote:
(...) By contrast, stepping only happens if your local clock is just set incorrectly and the re-sync delta has more to do with administrative error or failed batteries than differences in timekeeping accuracy. Are you talking about CLOCKREALTIME or CLOCKMONOTONIC? My understanding is: CLOCKREALTIME is both stepped and slewed. CLOCKMONOTONIC is slewed, but not stepped. CLOCKMONOTONICRAW is neither slewed nor stepped.
Sorry, I realize I should cite my source.
This mailing list post talks about all three together: <http://www.spinics.net/lists/linux-man/msg00973.html>
Although the documentation one can find by searching around the web is really bad. It looks like many of these time features were introduced, to Linux at least, with no documentation.
-glyph
- Previous message: [Python-Dev] Use QueryPerformanceCounter() for time.monotonic() and/or time.highres()?
- Next message: [Python-Dev] [Python-checkins] cpython (3.2): Issue #14409: IDLE doesn't not execute commands from shell with default
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]