Re: strange behaviour of ntp peerstats entries.

Brian Utterback wrote:
[]
I mis-spoke. It is actually the case that NTP prefers the sample of
the eight from any one single source that has the least delay. After
the sample is chosen, the samples from all the servers are then
subjected to different criteria to determine which will be the final
choice. Jitter and stratum both factor in.

Brian Utterback

Thanks for that clarification, Brian.

David


.

Relevant Pages

  • Re: strange behaviour of ntp peerstats entries.
    ... Brian Utterback wrote: ... Well, since the maximum error in transmitting time from server to client is one half the round trip delay, it is usually wise to try to minimize that delay. ... the stated conditions are NOT where I would look first for best performance. ...
    (comp.protocols.time.ntp)
  • Re: strange behaviour of ntp peerstats entries.
    ... Brian Utterback wrote: ... system I am using has servers whose delays are 51ms to 94. ... The offsets of all these servers agree to within 9ms. ... ago where a server with a little more jitter and much more delay was ...
    (comp.protocols.time.ntp)
  • Re: More Granularity in the US in the NTP Pool
    ... Hal Murray wrote: how do you decide which of two servers is "better"? ... something that averaged over some time period, ... Brian Utterback ...
    (comp.protocols.time.ntp)