On 2015-02-12 03:00, Rob wrote:
catherine.wei1...@gmail.com <catherine.wei1...@gmail.com> wrote:
Yes,I just tested it and found that the synchronization of NTP is really slow.
That is because ntpd is not designed to correct arbitrary errors that
you have applied externally. It is designed to lock to the correct time
and stay locked to that (within a few milliseconds when you use the network,
or within a few microseconds when you have a local reference).
The typical "acceptance test" scenario of "let's set the clock one hour
wrong while the system is running and see that ntpd corrects it" just is
not going to work. Drop that test, it should not be on the test list
for ntpd. When you need that test, use another product.
The test should be:
set the clock one hour wrong;
start ntpd -g;
measure how long it takes to get within 128ms, 64ms, 32ms, 16ms, ... of UTC;
measure offset, jitter, and wander throughout the next 24 hours;
perhaps load test with 1, 10, 100, ... clients running every 16...64 seconds,
while measuring process CPU and port 123 network loads.
Sounds like some work including setup, data collection, and analysis. ;^>
--
Take care. Thanks, Brian Inglis
_______________________________________________
questions mailing list
questions@lists.ntp.org
http://lists.ntp.org/listinfo/questions
