View All Products
Compute
Storage
Databases
Networking
Developer Tools
Delivery
Security
Services
Industries
Pricing
Community
Engage With Us
Community ▶ Questions ▶ Bandwidth Speed
Log in to Ask a Question

Bandwidth Speed

general

Is it just me, or is the network speed declining lately? I ran wget tests going to /dev/null on 3 different nodes and was getting the following:

wget -O /dev/null http://cachefly.cachefly.net/100mb.test
--2012-01-22 18:49:43--  http://cachefly.cachefly.net/100mb.test
Resolving cachefly.cachefly.net... 205.234.175.175
Connecting to cachefly.cachefly.net|205.234.175.175|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 104857600 (100M) [application/octet-stream]
Saving to: `/dev/null'

100%[======================================>] 104,857,600 15.7M/s   in 6.7s

wget -O /dev/null http://cachefly.cachefly.net/100mb.test
--2012-01-22 18:50:41--  http://cachefly.cachefly.net/100mb.test
Resolving cachefly.cachefly.net... 205.234.175.175
Connecting to cachefly.cachefly.net|205.234.175.175|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 104857600 (100M) [application/octet-stream]
Saving to: `/dev/null'

100%[======================================>] 104,857,600 7.74M/s   in 13s 

wget -O /dev/null http://cachefly.cachefly.net/100mb.test
--2012-01-22 18:51:15--  http://cachefly.cachefly.net/100mb.test
Resolving cachefly.cachefly.net... 205.234.175.175
Connecting to cachefly.cachefly.net|205.234.175.175|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 104857600 (100M) [application/octet-stream]
Saving to: `/dev/null'

100%[======================================>] 104,857,600 1.86M/s   in 33s

I know I used to get much faster speeds, usually around 50-70M/s

Any thoughts?

22 Replies

which region are you in?

Newark

I'm getting the same speeds in London.

My Rackspace VM shows 70M/s.

I'm pretty sure when I moved the majority of my stuff from Rackspace I was getting higher speeds as well…

Exactly. I have 2 much lower end VPS's elsewhere for testing type purposes, and on one I get much faster speed than here.

You know I think you're right. I'm in Newark as well and when I just got my account I could have sworn I downloaded an Ubuntu CD image at ~100MB/s. I remember thinking to myself that my Linode had a gigabit connection to the Internet.

Nowadays I hardly see anything over 10MB/s but that is probably all anecdotal anyway. :?

````
wget -O /dev/null http://cachefly.cachefly.net/100mb.test
--2012-01-22 20:13:07-- http://cachefly.cachefly.net/100mb.test
Resolving cachefly.cachefly.net… 205.234.175.175
Connecting to cachefly.cachefly.net|205.234.175.175|:80… connected.
HTTP request sent, awaiting response… 200 OK
Length: 104857600 (100M) [application/octet-stream]
Saving to: â/dev/nullâ

100%[======================================>] 104,857,600 9.59M/s in 16s

Dallas here, use to get +70M/s also, 9.59M/s is still fast, but still a change.

wget -O /dev/null http://cachefly.cachefly.net/100mb.test
--2012-01-22 19:23:51-- http://cachefly.cachefly.net/100mb.test
Resolving cachefly.cachefly.net… 205.234.175.175
Connecting to cachefly.cachefly.net|205.234.175.175|:80… connected.
HTTP request sent, awaiting response… 200 OK
Length: 104857600 (100M) [application/octet-stream]
Saving to: "/dev/null"

100%[======================================>] 104,857,600 10.3M/s in 10s

````
From my dedicated server on a 100Mbps he.net line. Hosted in Kansas City.

So I just ran these tests on two Linodes.

Newark:

wget http://cachefly.cachefly.net/100mb.test
--2012-01-22 20:13:34--  http://cachefly.cachefly.net/100mb.test
Resolving cachefly.cachefly.net... 205.234.175.175
Connecting to cachefly.cachefly.net|205.234.175.175|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 104857600 (100M) [application/octet-stream]
Saving to: `100mb.test'

100%[================================================================================================>] 104,857,600 4.66M/s   in 23s

2012-01-22 20:13:57 (4.42 MB/s) - `100mb.test' saved [104857600/104857600]

Atlanta:

wget -O /dev/null http://cachefly.cachefly.net/100mb.test
--2012-01-22 20:17:42--  http://cachefly.cachefly.net/100mb.test
Resolving cachefly.cachefly.net... 205.234.175.175
Connecting to cachefly.cachefly.net|205.234.175.175|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 104857600 (100M) [application/octet-stream]
Saving to: `/dev/null'

100%[======================================>] 104,857,600 25.9M/s   in 4.0s

2012-01-22 20:17:46 (24.9 MB/s) - `/dev/null' saved [104857600/104857600]

The 2 Linodes in Newark that I just tested are performing equally poorly compared to the one in Atlanta.

Linode Staff

We have multiple 10 Gbit links into each of our datacenters' core networks.

Stuff like this is always going to be incidental since, alas, we don't control cachefly or what they do, nor to we control the Internet between your Linode and them.

For whatever it's worth, the board is green on our end.

-Chris

It appears I am not alone :)

Don't get me wrong, I agree it's still decent speed, but it's nowhere near what it was or what I would expect from a premium provider. On one of my nodes I only use about 30GB of my allocated 200GB/mo, but I have setup and update files that get downloaded frequently by customers and I do not want them to get sub-par download speeds.

@caker

cachefly is somewhat of a standard test. Can you suggest something else? Please don't think I am on here just ranting, but I am concerned.

Here is a wget from one node in Newark to another in Newark:

wget -O /dev/null http://www.*****.com/**/setup.exe
--2012-01-22 19:35:19--  http://www.*****.com/**/setup.exe
Resolving www.*****.com... 66.228.xx.xxx
Connecting to www.*****.com|66.228.xx.xxx|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 135758846 (129M) [application/x-msdos-program]
Saving to: `/dev/null'

100%[======================================>] 135,758,846 5.04M/s   in 25s     

2012-01-22 19:35:44 (5.10 MB/s) - `/dev/null' saved [135758846/135758846]

Please excuse the *'s and x's, but I don't want to publicly put that out there :)

Linode Staff

@u4ia:

Here is a wget from one node in Newark to another in Newark:
Which is to be expected since the outgoing NIC speed on a Linode, by default (which we can raise with justification), is limited to 50Mbits/sec (about 5-6MB/sec). So that speed is normal.

We don't control the Internet, unfortunately, so anything that goes via the Internet is going to be subject to its peculiarities.

My advice: if it's fast enough, don't worry about it.

-Chris

@caker

Ahh, I did not realize that, thank you for clearing that up.

@caker:

We don't control the Internet, unfortunately,
Who do we talk to about that?

:P

My Linode in London:

wget -O /dev/null http://cachefly.cachefly.net/100mb.test
--2012-01-23 02:57:00--  http://cachefly.cachefly.net/100mb.test
Resolving cachefly.cachefly.net... 140.99.94.175
Connecting to cachefly.cachefly.net|140.99.94.175|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 104857600 (100M) [application/octet-stream]
Saving to: “/dev/null”

100%[============================================================================================================>] 104,857,600 39.9M/s   in 2.5s

2012-01-23 02:57:02 (39.9 MB/s) - “/dev/null” saved [104857600/104857600]

> My advice: if it's fast enough, don't worry about it. In my case, it is fast enough. Googlebot takes 50-100ms to fetch any of my web pages so I'm fine with that :P

For what it's worth, from Dallas:

 wget -O /dev/null http://cachefly.cachefly.net/100mb.test
--2012-01-23 02:19:05--  http://cachefly.cachefly.net/100mb.test
Resolving cachefly.cachefly.net... 205.234.175.175
Connecting to cachefly.cachefly.net|205.234.175.175|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 104857600 (100M) [application/octet-stream]
Saving to: `/dev/null'

100%[======================================>] 104,857,600 52.4M/s   in 1.9s

2012-01-23 02:19:07 (52.4 MB/s) - `/dev/null' saved [104857600/104857600]

Newark:

$ wget -O /dev/null http://cachefly.cachefly.net/100mb.test 
--2012-01-23 11:23:01--  http://cachefly.cachefly.net/100mb.test
Resolving cachefly.cachefly.net... 205.234.175.175
Connecting to cachefly.cachefly.net|205.234.175.175|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 104857600 (100M) [application/octet-stream]
Saving to: “/dev/null”

100%[=================================================================>] 104,857,600 4.33M/s   in 22s     

2012-01-23 11:23:23 (4.49 MB/s) - “/dev/null” saved [104857600/104857600]

@bryantrv:

@caker:

We don't control the Internet, unfortunately,
Who do we talk to about that?
The US Congress, apparently.

Given that http://cachefly.cachefly.net/100mb.test exists in multiple locations (I'd presume), it might be worthwhile to include mtr or traceroute to try to isolate which location is being slow from where.

From my home in upstate NY, near Canada, I can saturate my pitiful cable modem off of what appears to be cachefly in Newark:

rtucker@witte:~$ wget -O /dev/null http://cachefly.cachefly.net/100mb.test
--2012-01-23 07:14:07--  http://cachefly.cachefly.net/100mb.test
Resolving cachefly.cachefly.net... 205.234.175.175
Connecting to cachefly.cachefly.net|205.234.175.175|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 104857600 (100M) [application/octet-stream]
Saving to: `/dev/null'

100%[======================================>] 104,857,600 1.13M/s   in 79s     

2012-01-23 07:15:26 (1.27 MB/s) - `/dev/null' saved [104857600/104857600]

rtucker@witte:~$ mtr --report cachefly.cachefly.net
HOST: witte                       Loss%   Snt   Last   Avg  Best  Wrst StDev
  1\. 192.168.1.1                   0.0%    10    0.4   0.4   0.4   0.4   0.0
  2\. cable-mac1.rochnyei-ar4003.n  0.0%    10   21.8  24.2  18.9  30.2   3.8
  3\. rdc-24-93-8-186.wny.northeas  0.0%    10   10.5  10.9   9.4  15.2   1.7
  4\. rdc-72-230-153-2.wny.northea  0.0%    10   15.2  12.3  10.1  15.2   2.1
  5\. rdc-72-230-153-245.wny.north  0.0%    10   15.2  15.6  13.8  18.9   1.6
  6\. ae1-0.albynyyf-rtr000.nyroc.  0.0%    10   17.7  20.1  17.7  28.1   3.2
  7\. 107.14.19.26                  0.0%    10   28.8  27.9  26.0  31.4   1.7
  8\. 107.14.17.169                 0.0%    10   28.7  28.5  26.3  32.9   1.8
  9\. xe-5-0-6.ar2.ewr1.us.nlayer.  0.0%    10   29.4  30.5  28.5  32.8   1.3
 10\. vip1.G-anycast1.cachefly.net  0.0%    10   26.9  29.2  26.9  32.3   1.6

From my Linode in Newark, I get higher than others' reported speeds from what appears to be cachefly in Toronto:

rtucker@framboise:~$ wget -O /dev/null http://cachefly.cachefly.net/100mb.test
--2012-01-23 07:14:25--  http://cachefly.cachefly.net/100mb.test
Resolving cachefly.cachefly.net... 205.234.175.175
Connecting to cachefly.cachefly.net|205.234.175.175|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 104857600 (100M) [application/octet-stream]
Saving to: `/dev/null'

100%[======================================>] 104,857,600 11.1M/s   in 11s     

2012-01-23 07:14:36 (9.17 MB/s) - `/dev/null' saved [104857600/104857600]

rtucker@framboise:~$ mtr --report cachefly.cachefly.net
HOST: framboise                   Loss%   Snt   Last   Avg  Best  Wrst StDev
  1\. 207.99.1.13                   0.0%    10    3.2   2.0   0.5  13.1   4.0
  2\. 207.99.53.41                  0.0%    10    1.3   0.6   0.4   1.3   0.3
  3\. vlan801.tbr1.mmu.nac.net      0.0%    10    0.4   0.5   0.3   0.9   0.2
  4\. 0.e1-2.tbr1.ewr.nac.net       0.0%    10    0.9   1.6   0.9   5.0   1.3
  5\. gw-prioritycolo.torontointer  0.0%    10   23.0  26.8  22.8  61.6  12.2
  6\. vip1.G-anycast1.cachefly.net  0.0%    10   22.9  22.9  22.7  23.0   0.1

So yup; Internet. As long as this baby still hits 88 Mb/sec, life's probably OK…

Another thing to consider is how Cachefly is actually, erm, well, caching!

Case in point:

Test #1

wget -O /dev/null http://cachefly.cachefly.net/100mb.test
--2012-01-23 10:46:55--  http://cachefly.cachefly.net/100mb.test
Resolving cachefly.cachefly.net... 205.234.175.175
Connecting to cachefly.cachefly.net|205.234.175.175|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 104857600 (100M) [application/octet-stream]
Saving to: `/dev/null'

100%[======================================>] 104,857,600 1.88M/s   in 54s

2012-01-23 10:47:50 (1.85 MB/s) - `/dev/null' saved [104857600/104857600]

Test #2

wget -O /dev/null http://cachefly.cachefly.net/100mb.test
--2012-01-23 10:53:31--  http://cachefly.cachefly.net/100mb.test
Resolving cachefly.cachefly.net... 205.234.175.175
Connecting to cachefly.cachefly.net|205.234.175.175|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 104857600 (100M) [application/octet-stream]
Saving to: `/dev/null'

100%[======================================>] 104,857,600 24.3M/s   in 5.0s

2012-01-23 10:53:36 (19.9 MB/s) - `/dev/null' saved [104857600/104857600]

If the closest cdn node doesn't have a copy, you get a slower one from farther away. Once that was cached, the next request was a lot faster.

[Edit]

This was from Newark, btw.

wget http://cachefly.cachefly.net/100mb.test
--2020-06-12 14:15:11--  http://cachefly.cachefly.net/100mb.test
Resolving cachefly.cachefly.net (cachefly.cachefly.net)... 167.88.158.176
Connecting to cachefly.cachefly.net (cachefly.cachefly.net)|167.88.158.176|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 104857600 (100M) [application/octet-stream]
Saving to: ‘100mb.test’

100mb.test                   100%[===========================================>] 100.00M   121MB/s    in 0.8s    

2020-06-12 14:15:12 (121 MB/s) - ‘100mb.test’ saved [104857600/104857600]

not bad. It was from Singapore.

wget -O /dev/null http://cachefly.cachefly.net/100mb.test
--2020-08-01 23:33:26-- http://cachefly.cachefly.net/100mb.test
Resolving cachefly.cachefly.net (cachefly.cachefly.net)… 205.234.175.175
Connecting to cachefly.cachefly.net (cachefly.cachefly.net)|205.234.175.175|:80… connected.
HTTP request sent, awaiting response… 200 OK
Length: 104857600 (100M) [application/octet-stream]
Saving to: ‘/dev/null’

/dev/null 100%[==============================================================>] 100.00M --.-KB/s in 0.1s

2020-08-01 23:33:26 (673 MB/s) - ‘/dev/null’ saved [104857600/104857600]

Reply

Please enter an answer
Tips:

You can mention users to notify them: @username

You can use Markdown to format your question. For more examples see the Markdown Cheatsheet.

> I’m a blockquote.

I’m a blockquote.

[I'm a link] (https://www.google.com)

I'm a link

**I am bold** I am bold

*I am italicized* I am italicized

Log in to Reply
Community Code of Conduct