Linode Forum
Linode Community Forums
 FAQFAQ    SearchSearch    MembersMembers      Register Register 
 LoginLogin [ Anonymous ] 
Post new topic  Reply to topic
Author Message
 Post subject:
PostPosted: Mon Jan 23, 2012 5:19 am 
Offline
Senior Member

Joined: Wed Apr 11, 2007 8:23 pm
Posts: 76
For what it's worth, from Dallas:

Code:
 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]


Top
   
 Post subject:
PostPosted: Mon Jan 23, 2012 6:26 am 
Offline
Senior Member

Joined: Mon Dec 07, 2009 6:46 am
Posts: 331
Newark:

Code:
$ 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]


Top
   
 Post subject:
PostPosted: Mon Jan 23, 2012 6:45 am 
Offline
Senior Member
User avatar

Joined: Fri Oct 24, 2003 3:51 pm
Posts: 965
Location: Netherlands
bryantrv wrote:
caker wrote:
We don't control the Internet, unfortunately,

Who do we talk to about that?

The US Congress, apparently.

_________________
/ Peter


Top
   
 Post subject:
PostPosted: Mon Jan 23, 2012 8:21 am 
Offline
Senior Member
User avatar

Joined: Sat Aug 30, 2008 1:55 pm
Posts: 1739
Location: Rochester, New York
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:

Code:
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:

Code:
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...


Top
   
 Post subject:
PostPosted: Mon Jan 23, 2012 11:58 am 
Offline
Junior Member
User avatar

Joined: Mon Jun 20, 2011 8:54 am
Posts: 44
Another thing to consider is how Cachefly is actually, erm, well, caching!

Case in point:
Test #1
Code:

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
Code:

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.


Top
   
Display posts from previous:  Sort by  
Post new topic  Reply to topic


Who is online

Users browsing this forum: No registered users and 2 guests


You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum

Search for:
Jump to:  
RSS

Powered by phpBB® Forum Software © phpBB Group