Re: how to analyze clock drift

[Emanuel Berg <embe8573@student.uu.se>]

Emanuel Berg <embe8573@student.uu.se> writes:

> Is that considered reliable to the point it makes
> sense diagnosing sleep_until with that instead of
> the C++'s now()?

On the other hand, isn't that from where now() gets
its data?

I have checked the following docs:

    http://en.cppreference.com/w/cpp/chrono/system_clock/now
    http://en.cppreference.com/w/cpp/thread/sleep_until

For sleep_until, they say:

    The clock tied to sleep_time is used, which means
    that adjustments of the clock are taken into
    account. Thus, the duration of the block might,
    but might not, be less or more than sleep_time -
    Clock::now() at the time of the call, depending on
    the direction of the adjustment. The function also
    may block for longer than until after sleep_time
    has been reached due to scheduling or resource
    contention delays.

But for now(), they don't say one word it should be
unreliable so it should be enough to diagnose
sleep_until.

-- 
underground experts united