On Friday, May 26, 2023 at 4:37:48 PM UTC-4, Edward McGuire wrote: > Periodic invitations might be expected to create an unwanted load on the NPP > (Pool Project) servers and the selected peers, but I also increased maxpoll > to lower the load to much, much less than a typical NTP server using NPP. The > typical server with, say, 7 pool peers and operating at a poll interval of > 1024 seconds would transmit a packet on average every 146 seconds. Whereas > the trial server tended to collect 24 peers and operate a a pool interval of > 32768 seconds, meaning it transmitted a packet on average ever 1365 seconds. > This is one tenth of the load put on the NPP by a default-configured NTP > server. > > Summary of parameter changes: > pool pool.ntp.org maxpoll 15 > tos maxdist 0.05 minsane 5 minclock 11 maxclock 12
The documentation suggests using no higher than maxpoll 10 on systems with a continuous internet connection. The higher polling intervals are meant for systems stuck with intermittent connectivity to keep costs down, such as when using a long-distance dialup time service or a pay-by-the-byte internet connection where a maxpoll of 17 makes sense. That's also a situation where "burst" (not iburst) makes sense as it sends several queries each poll, giving more samples to the clock filter process to hold over ntpd for the day-and-a-half poll 17. Cheers, Dave Hart -- This is questions@lists.ntp.org Subscribe: questions+subscr...@lists.ntp.org Unsubscribe: questions+unsubscr...@lists.ntp.org
