Rick164, on Feb 18 2008, 06:56 PM, said:
It selects the mirrors at random, what could happen is that you connect to a slow or distant server(europe <-> USA) and a timeout occurs.
No easy way to control this atm, we are filtering the crappy mirrors already though
PS: The statistics show a steady increase in downloads
, 7-8 terabyte monthly depending on the updates.
PING www.asus.com.tw (66.238.93.162) 56(84) bytes of data.
64 bytes from 66.238.93.162.ptr.us.xo.net (66.238.93.162): icmp_seq=1 ttl=243 time=160 ms
FRA-SuperDonkey10
PING 88.191.22.205 (88.191.22.205) 56(84) bytes of data.
64 bytes from 88.191.22.205: icmp_seq=1 ttl=54 time=40.1 ms
64 bytes from 88.191.22.205: icmp_seq=2 ttl=54 time=35.4 ms
USA-wwwsexeandcocom
PING 208.53.131.7 (208.53.131.7) 56(84) bytes of data.
64 bytes from 208.53.131.7: icmp_seq=1 ttl=55 time=123 ms
64 bytes from 208.53.131.7: icmp_seq=2 ttl=55 time=136 ms
USA-UnitedServerNo1
PING 66.90.73.253 (66.90.73.253) 56(84) bytes of data.
64 bytes from 66.90.73.253: icmp_seq=1 ttl=55 time=142 ms
64 bytes from 66.90.73.253: icmp_seq=2 ttl=55 time=140 ms
DEU-wwwusenextto
PING 80.252.110.147 (80.252.110.147) 56(84) bytes of data.
64 bytes from 80.252.110.147: icmp_seq=1 ttl=50 time=82 ms
64 bytes from 80.252.110.147: icmp_seq=2 ttl=50 time=77 ms
NLD-Razorback30
PING 85.17.52.92 (85.17.52.92) 56(84) bytes of data.
64 bytes from 85.17.52.92: icmp_seq=1 ttl=57 time=45.7 ms
64 bytes from 85.17.52.92: icmp_seq=2 ttl=57 time=43.3 ms
In Europe I have 25-50 ms..., 95% servers is in Europe ;p
My serwer use 0,3-0,5 TB / month , this is 1/8 max transfers.
(7-11K userów - plan max 25 K)- but transfer is not linear. 8 TB peer month is no big value. Aster is big cable provider in Poland - no command.com
--
SmOkPl