On 9/11/2012 15:01, Matt Joyce wrote:
While hopefully someone else will get back to you shortly with a more
definite answer, I strongly suspect that the transmission delay of the
NTP packets themselves would be too minimal to make much difference.
Usually around 76 bytes with ethernet overhead
ntpp...@arpage.org said:
Frontier has me provisioned at 6944kbit/s down and 1152kbit/s up, so it
presumably takes 179 µs to download an NTP packet vs. 1078 µs to upload one.
My interest here is mostly academic, though if I ever come into possession
of a GPS or WWV receiver I'd like to run a
On Monday, September 10, 2012 at 13:57, ntpp...@arpage.org wrote:
However, this server IS on an asymmetrical ADSL connection, 6mbit/s down
and 1mbit/s up
As I think I've mentioned before, I really think the effect of this is
overestimated -- or maybe it varies from connection to connection.
While hopefully someone else will get back to you shortly with a more
definite answer, I strongly suspect that the transmission delay of the
NTP packets themselves would be too minimal to make much difference.
Usually around 76 bytes with ethernet overhead included, transmission
over the DSL
6Mbps is 750,000 bytes/s so 86 bytes transmits in around 115µs and at 1Mbps
that time is closer to 688µs. So a difference of about half a milisecond.
Sounds about right.
If you are getting timing from something like GPS, you can measure that
offset.
If you are setting your clock from the
