[chrony-users] Comparing timekeeping performance with chronyd to ntpd |
[ Thread Index |
Date Index
| More chrony.tuxfamily.org/chrony-users Archives
]
- To: chrony-users@xxxxxxxxxxxxxxxxxxxx
- Subject: [chrony-users] Comparing timekeeping performance with chronyd to ntpd
- From: Watson Ladd <watson@xxxxxxxxxxxxxx>
- Date: Mon, 29 Apr 2019 17:27:12 -0700
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cloudflare.com; s=google; h=mime-version:from:date:message-id:subject:to; bh=R78rOXzsP6rlYcL9MJj/mzv3IGrubXERycRJ+c/5TMs=; b=h2L1xg5I8RpYlxqg/7DT8JD/2Yq4qLhINsKR+bJTnuUER3MfNxA/cvjfusV3aEhjCW AQco0gAhBzEeTjgV7WXjvu5RvsYjJy6SD38HRJMwogIYQN/wAfkRGO1qvZ/3RrzBw6ll qzo2EQ2JAYRh+ghEP5p2fxDjG28JquseqjdFk=
Dear all,
I'm trying to compare the performance of ntpd and chronyd in our
environment but am running into a snag. Our first thought was to look
at the offset measurements taken by each, but they don't seem to be
directly comparable: chronyd's are "spiky" while ntpd's are much
flatter. I wonder if there is internal smoothing in ntpd that isn't in
chrony. The kernel loop variables also behave differently, again
making comparison meaningless.
Is there a source I can look at for how to do such a comparison and
what statistics should be gathered to monitor timekeeping quality?
Ideally we would not need a GPS slaved machine to do the monitoring
and comparison, but methods that assume such a machine might also be
of interest if there is no other way to obtain the information.
Currently we are thinking of ntpd with the statistics command on on a
third machine, but don't really know how we would process the results.
Sincerely,
Watson Ladd
--
To unsubscribe email chrony-users-request@xxxxxxxxxxxxxxxxxxxx
with "unsubscribe" in the subject.
For help email chrony-users-request@xxxxxxxxxxxxxxxxxxxx
with "help" in the subject.
Trouble? Email listmaster@xxxxxxxxxxxxxxxxxxxx.