I'm forking the subject line, which didn't really seem relevant any more.
more below
On 3/18/2012 7:01 AM, David J Taylor wrote:
"Ron Frazier (NTP)" <[email protected]> wrote in message
news:[email protected]...
[]
Come to think of it, my comment about the polling interval not
increasing may only apply to a local refclock, not a local server.
You may be right - all the servers on this test system are Internet
servers.
Can you elaborate more about what NTPD_USE_INTERP_DANGEROUS does?
Sincerely,
Ron
Overnight results are here:
http://www.satsignal.eu/ntp/Win-8+Internet.html
As you can see, jitter is under a millisecond, with the local
(noselect) server showing about half a millisecond of jitter, and the
Internet servers between about 3 and just over 6 milliseconds.
From my point of view, those look pretty good. Those peerstats graphs
come in pretty handy.
NTPD_USE_INTERP_DANGEROUS if set, forces interpolation on Windows.
With Windows XP or earlier, Interpolation works well, but not on Vista
or later, so under certain conditions, NTP disables interpolation as
mentioned here:
http://lists.ntp.org/pipermail/questions/2011-November/030904.html
You can enable interpolation, and you may get better results. If not,
jitters will have a floor of about 0.977 milliseconds.
Cheers,
David
What's the dangerous part? Are we just talking lots of CPU churning?
If so, can I just shut down NTP and tweak it?
Sincerely,
Ron
--
(PS - If you email me and don't get a quick response, don't be concerned.
I get about 300 emails per day from alternate energy mailing lists and
such. I don't always see new messages very quickly. If you need a
reply and have not heard from me in 1 - 2 weeks, send your message again.)
Ron Frazier
timekeepingdude AT c3energy.com
_______________________________________________
questions mailing list
[email protected]
http://lists.ntp.org/listinfo/questions
