When I try to download a linux distribution to the server from mirror.stanford.edu, which can handle up to 100MB/Sec, the server only downloads at a max speed of 64KB/Sec.

I was wondering what speeds I should see for D/U, or is it the route?

Mark

wget ftp://ftp.uu.net/uumap.tar.Z
--01:03:02-- ftp://ftp.uu.net/uumap.tar.Z
=> `uumap.tar.Z'
Resolving ftp.uu.net... 192.48.96.9
Connecting to ftp.uu.net|192.48.96.9|:21... connected.
Logging in as anonymous ... Logged in!
==> SYST ... done. ==> PWD ... done.
==> TYPE I ... done. ==> CWD not needed.
==> SIZE uumap.tar.Z ... 8520221
==> PASV ... done. ==> RETR uumap.tar.Z ... done.
Length: 8520221 (8.1M)

100%[===============================================================================
===========>] 8,520,221 1.37M/s in 6.2s

01:03:13 (1.32 MB/s) - `uumap.tar.Z' saved [8520221]

But you should find you can max out your 100 Mbps (100 megabit per second not 100 megaByte per second) connection if you start a number of concurrent threads/downloads at once.

wget http://mirrors.liquidweb.com/CentOS/5.1/is...86-bin-6of6.iso
3% [==> ] 21,585,824 1.37M/s eta 6m 18s

wget http://mirror.steadfast.net/centos/5.1/iso...86-bin-6of6.iso
0% [ ] 811,008 62.8K/s eta 2h 25m

wget http://mirror.astate.edu/pub/centos/5.1/is...86-bin-6of6.iso
4% [===> ] 27,231,935 1.20M/s eta 7m 10s

wget http://centos.mirror.nac.net/5.1/isos/i386...86-bin-6of6.iso
0% [ ] 4,443,312 472K/s eta 26m 4s

wget http://mirrors.gigenet.com/centos/5.1/isos...86-bin-6of6.iso
4% [===> ] 24,096,516 1.66M/s eta 5m 17s

It is probably the route.

Mark

I don't think anything on a 100 mbps server is capped within the planet's datacenter, but it seems with increasing geographic distances we see different network performance limitations. When EV1 and The Planet were separate, I could get around 40 mbps on a single thread between the two with a single thread, but going to Michigan from Texas for example I would not see nearly that unless I did multiple concurrent threads. I'm not sure why the standford or my steadfast (chicago) test above is so slow though -- maybe someone else can give you a better analysis of the network route between the two and pinpoint the slowness if you're sure it's not on the stanford side (I'm not sure it's not on the steadfast side in my test above.)

Here's a comparison from another geographically-close (Dallas) provider to The Planet:

wget http://www.softlayer.com/test100.zip
--03:28:10-- http://www.softlayer.com/test100.zip
Resolving www.softlayer.com... 66.228.118.51
Connecting to www.softlayer.com|66.228.118.51|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 104874307 (100M) [application/zip]
Saving to: `test100.zip'

100%[=============================================>] 104,874,307 5.46M/s in 19s

If you download from that same above provider's Seattle datacenter however, you get a much (5x) slower result:

wget http://www.sea01.softlayer.com/downloads/test100.zip
--03:29:27-- http://www.sea01.softlayer.com/downloads/test100.zip
Resolving www.sea01.softlayer.com... 67.228.118.21
Connecting to www.sea01.softlayer.com|67.228.118.21|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 104874307 (100M) [application/zip]
Saving to: `test100.zip.1'

10% [===> ] 11,380,700 944K/s eta 99s


03:28:29 (5.26 MB/s) - `test100.zip' saved [104874307/104874307]