Re: Question about min/max poll and an interesting plot showing maxpoll's effect



Richard B. Gilbert wrote:

Ntpd is supposed to set it's own polling interval; something to do with
the "Allen Variance". My feeble understanding translates into English
as "short poll intervals allow ntpd to correct large errors quickly and
long poll intervals allow ntpd to correct small errors accurately".

Anyway, I'm a little surprised that shorter is better. I have two
machines as clients of my stratum 1 (GPS) server. All three are Sun
workstations; the server is an Ultra 10 440 MHz, one of the clients is
also an Ultra 10 440 MHz the other is an Ultra 5 360 MHz. All have been
running for several days. The Ultra 5 is polling at 64 second intervals
with an estimated error of 11056 us while the Ultra 10 is polling at 256
second intervals with an estimated error of 500 us.

The proper poll interval appears to be highly dependent on the quality
of the local clock.


My experience is that shorter is better with commodity hardware that is subject to rapid thermal
cycling - my home machines are in the basement which also houses the furnace - I can see the furnace
12 min on/off cycle in the frequency offset graphs. Equally when periodic compute intensive jobs
run (one of my S1's is also a file/backup server) the resultant thermal shock to the machine pushes
it way off - if I let ntpd poll long (or omit flag 3 on refclocks) it spends all it's time chasing
the thermal cycle and never quite makes it. Will a poll of 64 (or less on my own servers) it
catches it before it gets 250us off and corrects. My co-lo machines which have a much more even
load and are in an cabinet in a machine room show a dinural cycle that ntp copes with pretty well
even at a poll interval of 1024.

John
.



Relevant Pages

  • Re: The libntp resumee...
    ... Meantime I somehow I sought to convince me I should be able to convince myself that ntpq requests are served at a different priority than ntpd requests are. ... If you configured seven servers, you might observe ntpd using seven DIFFERENT poll intervals, one for each server because seven different servers will be reached by at least seven different network paths! ... When the other hosts synchronize to the entry hosts of our system, don't the other hosts ntpd know when and how much these entry hosts changed their time due to input? ...
    (comp.protocols.time.ntp)
  • Re: NTPD concurrent clients limit
    ... even if it is ntpd he is running, ... written by someone whose knowledge of ntp was gained in kindergarten class. ... NTP is designed to work with poll intervals between 64 seconds and 1024 ... After the initial burst, polling continues at intervals ...
    (comp.protocols.time.ntp)
  • Re: Question regarding loss of connection and ntpd not re-syncing the time.
    ... > of network connectivity; the ntpd daemon never re-syncs with its NTP ... If you are using DHCP on these machines and when you regain connectivity ... your DHCP server gives you another IP address you need to restart ntpd. ...
    (comp.protocols.time.ntp)
  • ntpd on FreeBSD
    ... After a power outaga, all our FreeBSD ... Nearly all of them had a problem though with ntpd. ... these machines booted before the the ntp servers came up. ... then restart ntpd. ...
    (freebsd-questions)
  • Re: NTP: time not synchronized
    ... we configure all others machines to synchronize on this time server. ... When I used monitor ntp, we can see that these machines have between 23 ... Large errors less that 1024 seconds can take a very long time to correct; the highest rate at which ntpd can slew the clock is 500 parts per million or about 43 seconds per day. ...
    (comp.protocols.time.ntp)