Re: [chrony-users] Root delay and Root dispersion values in `chronyc ntpdata' |
[ Thread Index |
Date Index
| More chrony.tuxfamily.org/chrony-users Archives
]
- To: chrony-users@xxxxxxxxxxxxxxxxxxxx
- Subject: Re: [chrony-users] Root delay and Root dispersion values in `chronyc ntpdata'
- From: Miroslav Lichvar <mlichvar@xxxxxxxxxx>
- Date: Thu, 10 Aug 2017 15:49:39 +0200
- Authentication-results: ext-mx01.extmail.prod.ext.phx2.redhat.com; dmarc=none (p=none dis=none) header.from=redhat.com
- Authentication-results: ext-mx01.extmail.prod.ext.phx2.redhat.com; spf=fail smtp.mailfrom=mlichvar@xxxxxxxxxx
- Dmarc-filter: OpenDMARC Filter v1.3.2 mx1.redhat.com 2700169F19
On Thu, Aug 10, 2017 at 01:22:25PM +0300, Horia Muntean wrote:
> The root dispersion just after a clock update contains what the server
> reports right ?
It includes dispersion that accumulated since the best measurement was
made (it doesn't have to be the last one) and also peer dispersion of
the measurement.
> In my opinion the values (root delay end dispersion) taken just after
> the clock update
> along with a short update interval (less than few seconds) would give
> a good max. error estimate.
> In a short amount of time between the updates the root dispersion
> should not increase too much.
If the network is heavily loaded, chronyd may drop a large number of
consecutive measurements.
I think what people are interested in is the maximum possible error of
the clock at any time, not just the points when the clock was updated.
If we know at time t the error was 10 +/- 50 microseconds and at time
t+100 (seconds) it was -20 +/- 70 microseconds, what can we say about
t+1, t+50 and t+99, if we assume the frequency of clock is accurate to
1 ppm?
--
Miroslav Lichvar
--
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.