A RetroSearch Logo

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Search Query:

Showing content from https://mail.python.org/pipermail/python-dev/2012-March/118341.html below:

[Python-Dev] Use QueryPerformanceCounter() for time.monotonic() and/or time.highres()?

[Python-Dev] Use QueryPerformanceCounter() for time.monotonic() and/or time.highres()?Glyph glyph at twistedmatrix.com
Sat Mar 31 04:28:26 CEST 2012
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 CLOCK_REALTIME or CLOCK_MONOTONIC?
> 
> My understanding is:
> 
> CLOCK_REALTIME is both stepped and slewed.
> 
> CLOCK_MONOTONIC is slewed, but not stepped.
> 
> CLOCK_MONOTONIC_RAW 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
More information about the Python-Dev mailing list

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4