Can't upload via ftp at more than 60kb/s

Does anyone else have this problem? That you can't upload at over 60kb/s even though your connection is faster than that? I have tested other ftp sites and I can upload at around 80-90kb/s.

I contacted dreamhost's support, and they claimed that it was my ISP, so I went to a few freinds houses that had diffrent ISP's and the same upload speeds or better to other sites (80-90kb/s) and found that I couldn't upload at more than 60kb/s.

I tested with Verizon DSL (3000/768) RoadRunner (8000/768) and GWI (5000/1024).

Please let me know if you also have these problems.

I've been able to upload at much faster than 60KB/s (that's kilobytes a second). I'm on the east coast of the U.S.

There are lots of reasons for a 33% difference. Where are you geographically located?

Like lensman said, routing and latency alone can more than account for that much variance in upload speed. wink

--rlparker

Right, but different ISP's have different routing backbones.

If you could please show a screenshot of your uploading to your DH site, please do that.

Also, I am on the eastcoast.

My latency is great to other places other than dreamhost, therefore I really believe that it is their problem.

Pinging to DH:
Reply from 66.33.201.141: bytes=32 time=107ms TTL=54
Reply from 66.33.201.141: bytes=32 time=106ms TTL=54
Reply from 66.33.201.141: bytes=32 time=106ms TTL=54
Reply from 66.33.201.141: bytes=32 time=107ms TTL=54

Pinging to Google:

Reply from 72.14.207.99: bytes=32 time=43ms TTL=242
Reply from 72.14.207.99: bytes=32 time=41ms TTL=242
Reply from 72.14.207.99: bytes=32 time=44ms TTL=242
Reply from 72.14.207.99: bytes=32 time=45ms TTL=242

And they are both in the same state (california) I am in maine.

Edited by gregory on 09/18/07 01:48 PM (server time).

Don't use google as an example. They run a very sophisticated edge network. Their domains will "resolve" to machines in different physical locations depending on where you are.

What's the tracert to dreamhost and other sites you're benchmarking dreamhost against?

Notice how alter.net has much higher latency while going through DH than any other host.

DH:
[code]
over a maximum of 30 hops:

1 11 ms 11 ms 11 ms 10.21.5.1
2 12 ms 11 ms 11 ms so-1-1-0-0.CORE-RTR1.PORT.verizon-gni.net [130.8
1.13.81]
3 13 ms 12 ms 13 ms 130.81.20.88
4 15 ms 15 ms 16 ms so-3-0-0-0.BB-RTR1.BOS.verizon-gni.net [130.81.2
0.172]
5 18 ms 19 ms 18 ms 0.so-5-2-0.XL1.BOS4.ALTER.NET [152.63.19.129]
6 105 ms 105 ms 105 ms 0.so-6-0-0.XL1.LAX15.ALTER.NET [152.63.112.53]
7 105 ms 105 ms 105 ms POS6-0.GW2.LAX15.ALTER.NET [152.63.117.89]
8 190 ms 204 ms 220 ms internapGIGE-gw.customer.alter.net [157.130.236.
110]
9 104 ms 106 ms 107 ms border1.po2-bbnet2.ext1a.lax.pnap.net [216.52.25
5.95]
10 101 ms 99 ms 99 ms newdream-1.border1.ext1a.lax.pnap.net [216.52.22
0.78]
11 105 ms 106 ms 106 ms dreamhost.com [66.33.201.141]
12 106 ms 106 ms 106 ms dreamhost.com [66.33.201.141]

1and1:
1 11 ms 11 ms 12 ms 10.21.5.1
2 11 ms 12 ms 13 ms so-1-1-0-0.CORE-RTR2.PORT.verizon-gni.net [130.8
1.13.85]
3 12 ms 12 ms 12 ms 130.81.20.89
4 15 ms 12 ms 12 ms so-0-0-0-0.CORE-RTR1.PWM01.verizon-gni.net [130.
81.18.158]
5 15 ms 14 ms 15 ms so-3-0-0-0.BB-RTR1.BOS.verizon-gni.net [130.81.2
0.172]
6 17 ms 15 ms 16 ms 0.so-5-1-0.XL1.BOS4.ALTER.NET [152.63.16.69]
7 23 ms 24 ms 23 ms 0.so-6-3-0.XL3.NYC4.ALTER.NET [152.63.0.69]
8 24 ms 23 ms 24 ms GigabitEthernet6-0-0.GW18.NYC4.ALTER.NET [152.63
.22.225]
9 24 ms 25 ms 32 ms teliasonera-test.customer.alter.net [157.130.255
.206]
10 26 ms 27 ms 26 ms schlund-118342-nyk-b1.c.telia.net [213.248.95.70
]
11 194 ms 218 ms 199 ms vl-402.gw-core-a.nyc.oneandone.net [217.160.229.
104]
12 74 ms 74 ms 75 ms ge-2-11.bb-a.ga.mkc.us.oneandone.net [212.227.12
0.226]
13 76 ms 75 ms 75 ms te-1-1.bb-a.slr.lxa.us.oneandone.net [74.208.1.6
5]
14 75 ms 75 ms 75 ms te-1-2.gw-dists-r5-a.slr.lxa.oneandone.net [74.2
08.1.115]
15 75 ms 76 ms 75 ms vl-987.gw-ps1.slr.lxa.oneandone.net [74.208.1.13
3]
16 77 ms 75 ms 75 ms 1and1.com [217.160.232.1]

HostGator:

Tracing route to hostgator.com [67.18.54.2]
over a maximum of 30 hops:

1 12 ms 11 ms 12 ms 10.21.5.1
2 14 ms 11 ms 11 ms so-1-1-0-0.CORE-RTR2.PORT.verizon-gni.net [130.8
1.13.85]
3 12 ms 12 ms 12 ms 130.81.20.89
4 13 ms 13 ms 13 ms so-0-0-0-0.CORE-RTR1.PWM01.verizon-gni.net [130.
81.18.158]
5 15 ms 15 ms 14 ms so-3-0-0-0.BB-RTR1.BOS.verizon-gni.net [130.81.2
0.172]
6 16 ms 16 ms 16 ms 0.so-5-1-0.XL1.BOS4.ALTER.NET [152.63.16.69]
7 23 ms 24 ms 23 ms 0.so-6-3-0.XL3.NYC4.ALTER.NET [152.63.0.69]
8 24 ms 24 ms 24 ms 0.ge-6-1-0.BR3.NYC4.ALTER.NET [152.63.3.166]
9 24 ms 25 ms 24 ms 204.255.174.74
10 31 ms 34 ms 35 ms as-0.r21.asbnva01.us.bb.gin.ntt.net [129.250.2.9
]
11 67 ms 68 ms 67 ms p64-3-1-0.r20.dllstx09.us.bb.gin.ntt.net [129.25
0.5.24]
12 66 ms 67 ms 67 ms po-1.r02.dllstx09.us.bb.gin.ntt.net [129.250.2.1
54]
13 68 ms 68 ms 67 ms xe-4-4.r03.dllstx09.us.ce.gin.ntt.net [157.238.2
25.6]
14 68 ms 67 ms 68 ms te7-1.dsr02.dllstx3.theplanet.com [70.87.253.18]

15 69 ms 68 ms 68 ms 7e.fd.5746.static.theplanet.com [70.87.253.126]

16 67 ms 66 ms 66 ms vl1.asr01.dllstx2.theplanet.com [12.96.160.26]
17 68 ms 135 ms 67 ms gi0-2.car16.dllstx2.theplanet.com [69.41.250.78]

18 68 ms 68 ms 68 ms gator.hostgator.com [67.18.54.2]
[/code]

ALSO, I can ping a site in the netherlands in just 1ms more than you guys!

Reply from 77.235.41.32: bytes=32 time=108ms TTL=51

Edited by gregory on 09/18/07 02:06 PM (server time).

In reply to:
If you could please show a screenshot of your uploading to your DH site, please do that.

What exactly do you want a screenshot of?

The ping is not really as relevant as a full traceroute, preferably several traceroutes taken over a period of time.

*That* much more accurately reflects your routing /latency conditions. wink

--rlparker

It looks to me very much like the *biggest* difference is which alter.net routers are used ...and that happens *before* getting to DH, not "going through" it wink

--rlparker

I want a screenshot of somebody uploading to dreamhost at more thAN 60KB/s

Than why can't DH contact alter.net and say they have a problem?

There is way too much "sensitive info" on my FTP screen for a "screenshot" without me doing more "sanitizing" than I am willing to take the time to do, but my results "1 minute ago" uploading a 40 MB file with a single FTP thread over my AT*T/SBC 6 mbps/768 connection form California to my DH hosted server averaged right at 75-76 kb/s.

--rlparker

Well, have you asked them? alter.net's problem is not DH's problem - your ISP routed you through alter.net. wink

--rlparker

I have sent a request to DH but they just said it was my ISP's problem. My ISP said that they didn't have any control over that.

I guess I will contact my ISP again.
On the other hand How do I go about installing shoutcast on my server?

In reply to:
I have sent a request to DH but they just said it was my ISP's problem.

Yeah, I'm afraid from what your traceroutes are showing I'd have to agree with them on that one. frown

In reply to:
My ISP said that they didn't have any control over that.

They might not, but they should be able to at least investigate and lobby for alter.net to check out their routers, on the basis that it is impacting their (your ISP's) customers connectivity. Unfortunately, this is all too typical of what you can expect in such situation from most ISP's.

It can't hurt to contact your ISP again; if enough people complain, with traceroutes to clearly indicate the problem, they may be inspired to tryo to get it fixed. wink

In reply to:
On the other hand How do I go about installing shoutcast on my server?

You can't, on a DreamHost shared server account. Installing a shoutcast server is specifically prohibited in the TOS.

I understand that the new DreamHost PS may allow that, and you can certianly do it on a dedicated server.

--rlparker

Thanks

You are welcome!

--rlparker

If you're on the east coast of the US, your latency to the DreamHost datacenter of ~100 ms is normal (at least to me). Do you know where the hostgator and 1and1 data centers are where your webserver would be?

BTW, I just got 103 KB/sec upload from our midwest office VPN to our NY firewall and back across the country to Los Angeles. My latency through this mess is 140 ms.

ncftp / > put mysql-5.0.45/client/mysql.exe
mysql-5.0.45/client/mysql.exe: 572.61 kB 174.31 kB/s
ncftp / >

why do you care about 30k/second?

Can't upload via ftp at more than 60kb/s