Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!usc!zaphod.mps.ohio-state.edu!tut.cis.ohio-state.edu!ucbvax!udel.edu!Mills
From: Mills@udel.edu
Newsgroups: comp.protocols.time.ntp
Subject: Re:  xntpd packets dropped
Message-ID: <9103222031.aa06120@huey.udel.edu>
Date: 23 Mar 91 01:31:54 GMT
Sender: daemon@ucbvax.BERKELEY.EDU
Distribution: inet
Organization: The Internet
Lines: 17

Debbie,

40-50 chimers per server does not sound like a significant
load. I see something like 200 now per fuzzball primary
server and they seen to grunt along without dropping many
packets, usually none. However, if you have changed the min-
poll value or max-poll value, you have defeated the automatic
poll interval calculation, which starts out at 64 seconds and
then ratchets back to 1024 seconds as conditions permit. 
In NTP Version 2, which you are running now, the poll interval
is clamped to 64 seconds for the peer(s) a client is actually
synchronized to; while in NTP Version 3, even those peers
ratchet up as well. You may address your cards and letters
to the implementors of a v3 daemon, should they care to
identify themselves.

Dave