I have seen it in the news page, seems like you are paying for dreamhost hosting. Nothing wrong with that, and it really seems like a nice offer.
The surprising thing is the claims about us.archive being slow from far away. As I'm writing this, I'm downloading from Europe 10 files at 2 mbit/s each (20 mbit/s total, 2 megabytes per second).
If download speed decreases as you get away from a server, the problem usually is the TCP receive window, which is the max. ammount of on-flight data (max speed = TCPRWin/ping). (It could be a saturated link between the server and you too, but that is much more strange)
This can be workarounded:
a) Getting many files at once (the limit is per TCP connection; that is, per download)
b) Using download accelerators (they request many parts of a file at once)
c) Increasing the TCP window
In Windows 9x/Me, the window was 8K by default, and in 2000/XP it is 16K, which is just ridiculous for fast connections (max. 16K/sec with 1000ms ping, 32 with 500, 100 with 166...). In Longhorn/Vista, it will be adaptive up to a maximum of 16 megs, that is, 1000 times bigger.
It can be changed creating a DWORD registry entry called TCPWindowSize in HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\ with the desired size as the value (a reasonable size to start is 256000, for example).
Contrary to popular belief, that is the only registry value you have to set, Windows will use window scaling automatically and will round the value to the nearest MSS size. A reboot is requered. To test the results, you can visit http://www.speedguide.net:8117 or just use ethereal to sniff you own traffic.
The default size for linux is 180K, I don't know about Macs.
Better dedicated hosting can get better speeds withouth doing this because they automatically serve the content from places that are close to the request, reducing the "ping" (well, RTT).
The surprising thing is the claims about us.archive being slow from far away. As I'm writing this, I'm downloading from Europe 10 files at 2 mbit/s each (20 mbit/s total, 2 megabytes per second).
If download speed decreases as you get away from a server, the problem usually is the TCP receive window, which is the max. ammount of on-flight data (max speed = TCPRWin/ping). (It could be a saturated link between the server and you too, but that is much more strange)
This can be workarounded:
a) Getting many files at once (the limit is per TCP connection; that is, per download)
b) Using download accelerators (they request many parts of a file at once)
c) Increasing the TCP window
In Windows 9x/Me, the window was 8K by default, and in 2000/XP it is 16K, which is just ridiculous for fast connections (max. 16K/sec with 1000ms ping, 32 with 500, 100 with 166...). In Longhorn/Vista, it will be adaptive up to a maximum of 16 megs, that is, 1000 times bigger.
It can be changed creating a DWORD registry entry called TCPWindowSize in HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\ with the desired size as the value (a reasonable size to start is 256000, for example).
Contrary to popular belief, that is the only registry value you have to set, Windows will use window scaling automatically and will round the value to the nearest MSS size. A reboot is requered. To test the results, you can visit http://www.speedguide.net:8117 or just use ethereal to sniff you own traffic.
The default size for linux is 180K, I don't know about Macs.
Better dedicated hosting can get better speeds withouth doing this because they automatically serve the content from places that are close to the request, reducing the "ping" (well, RTT).
Thread title:
