Sergio, thanks for the proof of why netselect is SO important...
Sergio Korlowsky wrote:
>
> > I'd LOVE to see mandrake updater use this.... it would
> > find the BEST mirror, not just the one you pick.
>
> I went to the web site downloaded the src file and compile it under
> cooker,
> so far I was able to ping several ftp servers... and you know whick one
> has the fastest response?
>
> ?[admin@xe2xpk admin]$ netselect -vv ftp.linux-mandrake.com
> ftp.linux-mandrake.com 169 ms 18 hops 100% ok (10/10)
> [ 473]
> 473 ftp.linux-mandrake.com
>
> [admin@xe2xpk admin]$ netselect -vv ftp.linuxberg.com
> ftp.linuxberg.com 212 ms 13 hops 90% ok ( 9/10)
> [ 540]
> 540 ftp.linuxberg.com
> [admin@xe2xpk admin]$
>
> [admin@xe2xpk admin]$ netselect -vv ftp.phys.ttu.edu
> ftp.phys.ttu.edu 210 ms 24 hops 90% ok ( 9/10)
> [ 792]
> 792 ftp.phys.ttu.edu
> [admin@xe2xpk admin]$
>
> BTW I am located in Texas, so this final one should faster (?)
Nope, not at all. As it turns out, ttu.edu is MANY more hops away...
for you to use them is a longer trip for the packets. The shortest
trip is ftp.linuxberg.com for you, and the fastest is linux-mandrake
itself. Now, at times, there might be faster paths, depending on
traffic,
but based on the number of hops, you would almost always be better off
using one of the other 2...
This is exactly why netselect is so great. It proves that the 'obvious'
server might not be the fastest or closest one.
Seth
