David J Taylor wrote: > "Why Tea" <[email protected]> wrote in message
> >> 2) If I were to do a trial run of ntpd on Windows 2003, how do >> I measure its ntpd performance in order to make a >> judgment? > > I use MRTG, Meinberg's monitor, and my own NTP Plotter package. > I think he was really asking about the parameters that you log and how you get them from ntpd. He is using ntpq to fetch the "offset" value. If ntpd is working well, this will be noise like and centred around zero. Under those circumstances, its jitter should be several times worse than the true jitter in the software clock. Windows applications' idea of th time will be compromised by the limitations of Windows, in particular its inability to interpolate between ticks, There may also be a systematic error due to network limitations, etc. If the offset is not noise like, the offset may be close to the actual clock error, as ntpd has poor transient response to things like temperature changes. _______________________________________________ questions mailing list [email protected] https://lists.ntp.org/mailman/listinfo/questions
