On 9/28/07, Ryan Malayter <[EMAIL PROTECTED]> wrote:
>
> I think weighting by something like netspeed^(1/3) (cube root) might
> be a good starting point. With that, a Gigabit-connected server would
> receive about 10 times the traffic of a T1-equipped server, rather
> than 667 times
>
I think this really should be loooked at soon. I am querying
pool.ntp.org from the USA, and at least two servers from the
155.101.3.0/24 netblock seem to be returned every time! This network
is the UNiversity of Utah, which seems to have a few servers in the
pool. But their netspeed settings seem to make them "hog" the pool.
Certainly sending 40% or more of all US pool traffic to the utah.edu
network is not desirable! Yes, they may have Gigabit connectivity, but
that bandiwdth is shared amongst a large number of users and
applications.
Also of note is that I am in Chicago, thousands of miles away from
Utah, so perhaps more granularity that country is desirable, at least
in the USA.
--
RPM
=========================
All problems can be solved by diplomacy, but ce and treachery are
equally effective, and more fun.
-Anonymous
_______________________________________________
timekeepers mailing list
[email protected]
https://fortytwo.ch/mailman/cgi-bin/listinfo/timekeepers
