From: Carsten Bormann <cabo@tzi.org>
To: Michael Yartys <michael.yartys@protonmail.com>
Cc: bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] Possibly interesting video on atomic clocks
Date: Tue, 24 Aug 2021 22:38:14 +0200 [thread overview]
Message-ID: <1FFEAE39-AB92-4355-BD4F-7AB334DB4B5E@tzi.org> (raw)
In-Reply-To: <Mpy1om4FfSS40eNMiYKUOFUGO0TO9aAR0rI21bZqW1aT0MF0dI-zuvjhl7yVwrLJH9KaNPQkuMkGZfeCsDDkBZow3IVB_xYZWcQtw4t5k1E=@protonmail.com>
On 2021-08-24, at 20:00, Michael Yartys via Bloat <bloat@lists.bufferbloat.net> wrote:
>
> https://www.youtube.com/watch?v=JK3eTGkX6qY
OMG. Among other things, he says:
A cheap Rubidium clock module has a deviation of less than 1 second in 100 million years (that would be 3e-16!) (1).
Because it’s an atomic clock, it sure must be radioactive (2).
NTP gives you 400 ms deviations (3).
Well, that should be enough to laugh this whole thing off.
However:
PTP is good (a), and support for it is in many chips (b).
It is useful to have a local time reference that is better than a crappy CPU clock crystal (c) (even if a Rubidium oscillator is overkill, in particular if you already have PTP to sync with — go for a cheap OCXO for a start).
Linus’ typical 254,481 views is going to get some attention to the question of precise clocks on computers — that is probably the only good coming from this video, together with complete garbage such as that your computer must be radioactive to give you a fair gaming experience.
Grüße, Carsten
prev parent reply other threads:[~2021-08-24 20:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-24 18:00 Michael Yartys
2021-08-24 20:38 ` Carsten Bormann [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://lists.bufferbloat.net/postorius/lists/bloat.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1FFEAE39-AB92-4355-BD4F-7AB334DB4B5E@tzi.org \
--to=cabo@tzi.org \
--cc=bloat@lists.bufferbloat.net \
--cc=michael.yartys@protonmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox