Hi Ok, to be 1000: 1, you would take the 0.2 to 0.5 ms that you see on the LAN and take it up to 200 to 500ms. That's *way* worse than anything I have ever seen for a serial server over a LAN.
Bob On May 23, 2012, at 5:15 PM, Chris Albertson wrote: > On Wed, May 23, 2012 at 2:02 PM, Bob Camp <[email protected]> wrote: >> Hi >> >> What ever degradation the serial stream sees on the LAN, the resulting NTP >> output will see once it's on the same LAN. It's unlikely you will see more >> than a 2:1 net degradation no matter what is going on. The flywheel in the >> NTP algorithm will likely help you in this case to actually improve things a >> bit. > > Have you actually tried this and measured? 2:1 is very optimistic. > Typically it is 1000:1 or worse > > But you are right that it may not matter. For most uses if the > computer's clock is correct at the 0.1 second level they are happy. > but this is a "time nut" mailing list and some of us like to get NTP > to run at the uSecond level. Useless as that might be. > > > > Chris Albertson > Redondo Beach, California > > _______________________________________________ > time-nuts mailing list -- [email protected] > To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts > and follow the instructions there. _______________________________________________ time-nuts mailing list -- [email protected] To unsubscribe, go to https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts and follow the instructions there.
