[time-nuts] time.windows.com statistics

Max Robinson max at maxsmusicplace.com
Mon Jul 14 15:05:47 EDT 2014


I have set the time server to us.pool.ntp.org.  It's keeping my clock in 
step with the rest of the world so I am a happy camper.  I had no idea my 
simple question would result in such a long thread.

Regards.

Max.  K 4 O DS.

Email: max at maxsmusicplace.com

Transistor site http://www.funwithtransistors.net
Vacuum tube site: http://www.funwithtubes.net
Woodworking site 
http://www.angelfire.com/electronic/funwithtubes/Woodworking/wwindex.html
Music site: http://www.maxsmusicplace.com

To subscribe to the fun with transistors group send an email to.
funwithtransistors-subscribe at yahoogroups.com

To subscribe to the fun with tubes group send an email to,
funwithtubes-subscribe at yahoogroups.com

To subscribe to the fun with wood group send a blank email to
funwithwood-subscribe at yahoogroups.com

----- Original Message ----- 
From: "Chris Albertson" <albertson.chris at gmail.com>
To: "Discussion of precise time and frequency measurement" 
<time-nuts at febo.com>
Sent: Monday, July 14, 2014 11:00 AM
Subject: Re: [time-nuts] time.windows.com statistics


> On Mon, Jul 14, 2014 at 3:38 AM, Tim Shoppa <tshoppa at gmail.com> wrote:
>
>> Wonder out loud if using NTP server in a load-distributing cloud will 
>> just
>> intrinsically be randomly cruddy, or if this is somehow engineering a
>> source which is often good enough for SNTP users but obviously
>> inappropriate for NTP to prevent extra load from non-windows users.
>
> Pool servers seem to work well.  But they are randomly assigned only
> once.  Once a connection is made to a pool server it remains connected
> to the same server "for the duration".   Best practice is to use about
> five pool servers and let NTP sort out which are "best".  Even if
> using a GPS you should still configure about five pool servers.
>
> A load distributed load cloud where each data packet goes to a
> different server just plan would not work for NTP.  If you look at the
> clock selection algorithm the servers would all be rejected and NTP
> would likely fall back to the PC's internal clock as the best source.
> NTP's design depends on network path between any two NTP servers
> remaining mostly constant or at least changing slowly.  Load sharing
> would kill that assumption.
>
> -- 
>
> Chris Albertson
> Redondo Beach, California
> _______________________________________________
> time-nuts mailing list -- time-nuts at febo.com
> To unsubscribe, go to 
> https://www.febo.com/cgi-bin/mailman/listinfo/time-nuts
> and follow the instructions there. 




More information about the time-nuts mailing list