Abysmal network speed

#1

Just got into the beta and very excited!

However, I am getting horrible speeds just doing some wget and apt-get updates. Every speed test is maxing out at around 50KB/s. Most updates are going at 15KB/s.

This is on a subsonic and ridiculous instance. Cachefly is the only one that gets to 12MB/s, but nothing else gets there. I was assuming this would be gigabit or 10e on larger instances.

Maybe just a fluke right now? I’ll keep doing some testing.

edit to show my apt-get update:
53% [15 linux-firmware 8,658 kB/19.9 MB 44%] 34.0 kB/s 6min 3s

#2

Hrm, maybe you hit a slow mirror?

I’m getting almost 5MB/s doing an apt-get upgrade on a debian instance - https://gist.github.com/justinlund/e57a544b09f17b5f2f48

We’re using 10GbE and 120Gbps between pods. Link speeds on the instances are configured for 100mbit so you shouldn’t have a network bottleneck from a hardware perspective.

We’re also connected to fat pipes from several different bandwidth providers in the data center so that shouldn’t be the bottleneck either.

Keep us posted!

#3

Here is my Ridiculous configured instance doing a speedtest to linode west:

dhc-user@ridic1:~$ wget http://speedtest.fremont.linode.com/100MB-fremont.bin
–2014-07-23 19:17:03-- http://speedtest.fremont.linode.com/100MB-fremont.bin
Resolving speedtest.fremont.linode.com (speedtest.fremont.linode.com)… 2600:3c01::4b, 50.116.14.9
Connecting to speedtest.fremont.linode.com (speedtest.fremont.linode.com)|2600:3c01::4b|:80… connected.
HTTP request sent, awaiting response… 200 OK
Length: 104857600 (100M) [application/octet-stream]
Saving to: â100MB-fremont.binâ

0% [ ] 500,616 41.3KB/s eta 42m 59s

And here is the same test using dreamhost shared host:

[sassafras]$ wget http://speedtest.fremont.linode.com/100MB-fremont.bin
–2014-07-23 12:18:22-- http://speedtest.fremont.linode.com/100MB-fremont.bin
Resolving speedtest.fremont.linode.com… 2600:3c01::4b, 50.116.14.9
Connecting to speedtest.fremont.linode.com|2600:3c01::4b|:80… connected.
HTTP request sent, awaiting response… 200 OK
Length: 104857600 (100M) [application/octet-stream]
Saving to: â100MB-fremont.binâ

100%[======================================>] 104,857,600 38.3M/s in 2.6s

2014-07-23 12:18:25 (38.3 MB/s) - â100MB-fremont.binâ

Edit: Just did a test to my dreamobjects file, which should be able to max the transfer, and got maximum 35KB/s. :confused:
Edit2: Down to 16.6KB/s :frowning: Testing this on two separate instances.
1% [26 fonts-freefont-ttf 2,020 kB/4,140 kB 49%] 16.6 kB/s 8h 31min 19s

#4

Those slow speeds are really surprising on your instance.

When I tested on a lightspeed Ubuntu Trusty instance I was getting 3.5MB/s

dhc-user@trusty-1:~$ wget http://speedtest.fremont.linode.com/100MB-fremont.bin
–2014-07-23 23:01:01-- http://speedtest.fremont.linode.com/100MB-fremont.bin
Resolving speedtest.fremont.linode.com (speedtest.fremont.linode.com)… 2600:3c01::4b, 50.116.14.9
Connecting to speedtest.fremont.linode.com (speedtest.fremont.linode.com)|2600:3c01::4b|:80… connected.
HTTP request sent, awaiting response… 200 OK
Length: 104857600 (100M) [application/octet-stream]
Saving to: ‘100MB-fremont.bin’

100%[======================================>] 104,857,600 3.50MB/s in 30s

2014-07-23 23:01:31 (3.37 MB/s) - ‘100MB-fremont.bin’ saved [104857600/104857600]

A bit slower but still decent with a subsonic Debian instance:

dhc-user@jumpbox:~$ wget http://speedtest.fremont.linode.com/100MB-fremont.bin
–2014-07-23 23:08:10-- http://speedtest.fremont.linode.com/100MB-fremont.bin
Resolving speedtest.fremont.linode.com (speedtest.fremont.linode.com)… 2600:3c01::4b, 50.116.14.9
Connecting to speedtest.fremont.linode.com (speedtest.fremont.linode.com)|2600:3c01::4b|:80… connected.
HTTP request sent, awaiting response… 200 OK
Length: 104857600 (100M) [application/octet-stream]
Saving to: `100MB-fremont.bin’

100%[======================================>] 104,857,600 2.98M/s in 34s

2014-07-23 23:08:45 (2.92 MB/s) - `100MB-fremont.bin’ saved [104857600/104857600]

I’d recommend booting a new instance and see if you’re still having the same issue. We’ll do some further investigation to see if we can find a cause.

#5

3.5MB/s and 2.98M/s is still much slower than even my home connection. My $2/month vps I just tested will easily reach 60MB/s on the same link, and 107MB/s from the cachefly CDN. Perhaps the network is over congested? I’m not sure, but wanted to pass on my findings as unusual. I’ll try booting a new instance as you suggested.

#6

We’re doing some additional testing and we think there is an issue with your tenant router. We’re going to continue diagnosing it and figure out what’s going on.
[hr]
Try forcing IPv4 with wget -4 and see if you see a difference.

#7

It seems that my domain lookup is gone now. I can’t ping or wget any address:

dhc-user@ridic1:~$ ping google.com
ping: unknown host google.com

EDIT: Just booted up a new instance which is working:

dhc-user@testingsub1:~$ wget -4 http://speedtest.fremont.linode.com/100MB-fremont.bin
–2014-07-24 00:10:27-- http://speedtest.fremont.linode.com/100MB-fremont.bin
Resolving speedtest.fremont.linode.com (speedtest.fremont.linode.com)… 50.116.14.9
Connecting to speedtest.fremont.linode.com (speedtest.fremont.linode.com)|50.116.14.9|:80… connected.
HTTP request sent, awaiting response… 200 OK
Length: 104857600 (100M) [application/octet-stream]
Saving to: â100MB-fremont.binâ

100%[=======================================================================================>] 104,857,600 3.99MB/s in 24s

2014-07-24 00:10:51 (4.10 MB/s) - â100MB-fremont.binâ saved [104857600/104857600]

It’s definitely better, but still very slow compared to the shared hosting 1gbit port, and no where near the 100mbit port speed.

EDIT2: New instance is back to slow speeds. Seeing max 39KB/s.

#8

Just spent a few minutes testing and doing some more benchmarks. I compared these to my $2/month VPS located in LA (near dreamhost) and tested both on the Dreamhost network location (VPS shows 2200mi distance but it is wrong). Pay attention to the ping :open_mouth:

Here is the hyperspeed instance:

Testing from New Dream Network, LLC (173.236.252.113)…
Hosted by DreamHost (Los Angeles, CA) [37.84 km]: 42510.199 ms
Testing download speed…
Download: 0.19 Mbits/s
Testing upload speed…
Upload: 0.14 Mbits/s
Share results: http://www.speedtest.net/result/3646274000.png

Here is my $2 VPS:

Testing from ColoCrossing (198.46.###.##)…
Hosted by DreamHost (Los Angeles, CA) [3542.52 km]: 38.26 ms
Testing download speed…
Download: 373.37 Mbits/s
Testing upload speed…
Upload: 195.64 Mbits/s
Share results: http://www.speedtest.net/result/3646274675.png

#9

There is still an issue with your specific router that we’re still investigating. We’re also looking into why speeds are lower than expected too.

#10

Just wanted to post an updated on our progress. We’ve re-written our software routers and our doing some early testing now. We’re seeing much faster speeds and hope to get this into the hands of willing beta testers soon.

[code]dhc-user@test2:~$ wget -4 http://speedtest.fremont.linode.com/100MB-fremont.bin
–2014-08-14 14:33:16-- http://speedtest.fremont.linode.com/100MB-fremont.bin
Resolving speedtest.fremont.linode.com (speedtest.fremont.linode.com)… 50.116.14.9
Connecting to speedtest.fremont.linode.com (speedtest.fremont.linode.com)|50.116.14.9|:80… connected.
HTTP request sent, awaiting response… 200 OK
Length: 104857600 (100M) [application/octet-stream]
Saving to: ‘100MB-fremont.bin’

100%[================================================================================================================>] 104,857,600 53.7MB/s in 1.9s

2014-08-14 14:33:18 (53.7 MB/s) - ‘100MB-fremont.bin’ saved [104857600/104857600]
[/code]

#11

Ooh exciting.

I’ve been noticing issues with one of my server’s connections as well (I haven’t yet done the tests to see if it’s a network issue, but this thread is quite helpful for knowing what to try).

Consider me a willing beta tester :smiley:

#12

Both of your routers are now running on the rewritten code. Let me know how it works for you!

#13

Justin, I’ve been seeing this problem since the beginning too - really slow downloads from Centos yum repositories. I’m trying to install node.js on a Centos instance, and it looks like it’s going to take hours just to download the packages. Could you please advise me on how to proceed to improve this? My DreamCompute username is bobhar11. Thanks!

#14

The same problem and at me. My login: aleshi27
Screenshot

#15

We are planning to roll out the upgraded software routers this week. That should help with a lot of the speed issues most people are seeing.

We are also investigating some slowness with IPv6. You might try disabling IPv6 and see if you still have issues downloading from the repos.

#16

Hi Justin, did the upgraded software routers get rolled out yet? I’m seeing download speeds of 20-50kb/s on two instances I’ve launched, one subsonic CentOS, one lightspeed Ubuntu. I realize this is a free beta, but those transfer speeds don’t even make testing feasible.

#17

We did roll out the upgraded software routers. We’ve seen drastic speed improvements but still intermittent speed issues with IPv6. Can you try disabling IPv6 and let me know if there’s an increase in speed?