| Author |
Message |
caker
Joined: 15 Apr 2003
Posts: 2387
Location: Galloway, NJ
|
| Posted: Sun Feb 18, 2007 6:49 pm Post subject: East Coast Datacenter |
|
|
I'm pleased to announce that in addition to Fremont, CA and Dallas, TX datacenters, we now have machines located in Atlanta, GA. There are a few more details on the "Our Network" page. For latency comparison, you can ping 64.22.71.1 .
Please open a support ticket if you're interested in migrating to that datacenter.
-Chris |
|
| Back to top |
|
c1i77
Joined: 23 Sep 2004
Posts: 70
Location: Delft, Netherlands
|
| Posted: Mon Feb 19, 2007 3:09 am Post subject: Re: East Coast Datacenter |
|
|
Hi Chris,
It really is nice seeing Linode.com expanding out even further at your typically cautious rate :-).
caker wrote: ... For latency comparison, you can ping 64.22.71.1 ...
Nice -- from AMSIX (Amsterdam):
105ms ... AtlantaNAP
160ms ... HE.net Fremont
caker wrote: ... Please open a support ticket if you're interested in migrating to that datacenter.
Would migrating help with max bandwidth? The best I ever get when downloading from Fremont is round 200kbyte/sec. A test this morning (UTC) got me an average of 183kbyte/sec downloading a 30MB file[*]. It will definitely be worth the trouble if Linode/AtlantaNAP can improve on that.
Cliff
[*] For comparison a few minutes later I got an average 1.28Mbyte/sec from kernel.org -- max 1.96 Mbyte/sec, the top-speed of my ADSL line.
EDIT (Feb-22): After migrating to the Atlanta DC, my download rate improved by more than 35%. The same 30MB file downloaded at 250k/s average (254k/s max).
Hopefully it doesn't degrade over time. |
|
| Back to top |
|
TehDan
Joined: 25 Nov 2004
Posts: 40
|
| Posted: Mon Feb 19, 2007 10:04 am Post subject: |
|
|
Great news!
I assume this will require a change of IP? |
|
| Back to top |
|
Shermozle
Joined: 15 Apr 2004
Posts: 52
Location: London, UK
|
| Posted: Mon Feb 19, 2007 5:59 pm Post subject: West |
|
|
I thought about migrating to the West Coast data centre a while back, since it'd be closer to the fibres to Australia. Thing is, it's 20-30ms less ping, so not worth the effort.
Besides which, one of these days everything West of the San Andreas is gonna go kersplash and become Arizona Bay*. Better to be in Texas then, I reckon, though I suspect it might not do good things to connectivity to .au
*: http://en.wikipedia.org/wiki/Arizona_Bay |
|
| Back to top |
|
smiffy
Joined: 23 Jan 2007
Posts: 66
Location: 80 miles from Adelaide, Australia
|
| Posted: Mon Feb 19, 2007 11:52 pm Post subject: |
|
|
From Australia, ssh session from Fremont is slightly faster than Dallas, but both are quite useable - I've got slower responses from some of the older boxes on my LAN!
And The Big One is more likely to hit Southern California, from what I read last - may not affect Hurricane Electric too much. |
|
| Back to top |
|
tronic
Joined: 04 Dec 2004
Posts: 123
|
| Posted: Wed Feb 21, 2007 4:33 am Post subject: |
|
|
TehDan wrote: Great news!
I assume this will require a change of IP?
Yup, since you'd be changing to a new data center. |
|
| Back to top |
|
ross
Joined: 28 Sep 2005
Posts: 11
|
| Posted: Wed Feb 21, 2007 10:23 am Post subject: |
|
|
Is this the major announcement hinted at within the RAM upgrade thread?
No complaints, just wondering. |
|
| Back to top |
|
tasaro
Joined: 15 Apr 2003
Posts: 135
Location: Manahawkin, NJ
|
| Posted: Wed Feb 21, 2007 10:30 am Post subject: |
|
|
| This is not the major announcement hinted at within the RAM upgrade thread. . . |
|
| Back to top |
|
Xan
Joined: 08 Feb 2004
Posts: 310
Location: Austin
|
| Posted: Wed Feb 21, 2007 12:32 pm Post subject: |
|
|
tasaro,
I haven't had a chance to say welcome, and how it's nice to have another Linode staff member to help us out around here.
I'd like to suggest that you pick some distinctive avatar for the forums. We can all recognize Caker and Mike at a glance. My first reaction to your post here was "why would this guy know anything about it" until I caught the "Linode Staff" by your name. An avatar we could recognize would really help us to know when we're seeing an "official" response.
Edit: Funny, mine's not showing up on this post, and I can't go look at my profile without a prompt. Maybe there's some problem with the forum at the moment, and if so, please ignore me! |
|
| Back to top |
|
c1i77
Joined: 23 Sep 2004
Posts: 70
Location: Delft, Netherlands
|
| Posted: Thu Feb 22, 2007 6:12 am Post subject: |
|
|
Hi,
I just migrated my bundle of images to Atlanta. SSH'ing feels a lot snappier than Amsterdam<->Fremont.
FWIW, for others who are thinking of migrating their Linode(s), here are some of the notes I made:
* See Aaron's post about "Filtered ports at new datacenter".
* Prior to starting migration, set TTL in DNS to a low number for affected domains (Zoneedit.com permits a TTL 1200 [20mins] under "Configure SOA"). Ideally, wait for old TTL to expire before commencing the migration.
* transfer rate -- between 0800 and 1000 UTC -- Fremont -> Atlanta was roughly 40-50MB/min (1GB ~25mins) .
* disk image transfers are uncompressed, so shrink underutilized disk images to speed up the migration.
* New hosts are Ubuntu-based
(Linux hostXX.atlanta.linode.com 2.6.16.36-2-bigmem #1 SMP Tue Dec 26 13:58:52 EST 2006 i686 GNU/Linux).
* Reverse DNS and authorized keys have to be set again.
* After migrating, set TTL in DNS SOA to a more reasonable number again (e.g. 8600 = 1 day).
[EDIT: Feb-22]
* Replaced ftp.us.debian.org in /etc/apt/sources.list with http://ftp-mirror.internap.com/pub/debian/ -- a mere 3.2ms ping time away. This source also mirrors Ubuntu.)
Cliff |
|
| Back to top |
|
SteveG
Joined: 30 Nov 2003
Posts: 220
|
| Posted: Thu Feb 22, 2007 5:51 pm Post subject: |
|
|
c1i77 wrote:
(Lots of good stuff I snipped)
* After migrating, set TTL in DNS SOA to a more reasonable number again (e.g. 8600 = 1 day).
I assume that's a typo for 86400 = 1 day? |
|
| Back to top |
|
c1i77
Joined: 23 Sep 2004
Posts: 70
Location: Delft, Netherlands
|
| Posted: Fri Feb 23, 2007 12:54 am Post subject: |
|
|
SteveG wrote: I assume that's a typo for 86400 = 1 day?
Yes, you're right. Thanks for the heads-up -- I had in fact repeated it in my DNS. :oops:
Now set to the proper number for one day: 86400
Cliff |
|
| Back to top |
|
tofu
Joined: 01 Jul 2006
Posts: 29
Location: Ghent, Belgium
|
| Posted: Sun Feb 25, 2007 2:50 pm Post subject: |
|
|
Caker, could you please put a test file on a server in the new datacenter, so I can test the download speed?
I live in Belgium and want to see if I get a higher speed then on host 44 where I am now.
There is not much difference in the ping (now: 126 new DC: 111) |
|
| Back to top |
|
monarch
Joined: 05 Feb 2006
Posts: 22
Location: Sydney, Australia
|
| Posted: Thu Mar 01, 2007 10:56 am Post subject: Ping times from London |
|
|
Summary
It is about 64ms quicker from London to the East Coast (124ms) than the West Coast (188ms).
This is good news for European customers..!
From London to East Coast Linode:
Code: traceroute to 64.22.71.1 (64.22.71.1), 30 hops max, 38 byte packets
1 laptop (192.168.0.9) 2.283 ms 0.617 ms 0.616 ms
2 192.168.1.1 (192.168.1.1) 8.021 ms 3.058 ms 2.635 ms
3 89.242.240.1 (89.242.240.1) 31.365 ms * 31.854 ms
4 lg-200-413.rtr001.bre.opaltelecom.net (62.24.252.69) 33.163 ms 32.697 ms 34.440 ms
5 gig-9-1-rtr001.hex.opaltelecom.net (62.24.254.10) 32.868 ms 60.527 ms 33.895 ms
6 gig0-1-rtr002.hex.opaltelecom.net (62.24.196.38) 36.238 ms 33.155 ms 34.158 ms
7 195.66.226.167 (195.66.226.167) 33.729 ms 34.509 ms 84.530 ms
8 gnax.ge2-3.br01.atl01.pccwbtn.net (63.216.31.158) 122.409 ms 120.595 ms 122.019 ms
9 atl-core-e-gi4-4.gnax.net (209.51.131.30) 122.759 ms 122.463 ms 122.824 ms
10 atl-core-a-tgi2-1.gnax.net (209.51.149.105) 122.064 ms 173.207 ms 121.832 ms
11 l3-atl-18.gnax.net (209.51.131.74) 122.770 ms 122.131 ms *
From London to West Coast Linode:
Code: traceroute to ns.tuberant.com (64.62.190.85), 30 hops max, 38 byte packets
1 laptop (192.168.0.9) 1.499 ms 24.136 ms 24.991 ms
2 192.168.1.1 (192.168.1.1) 3.168 ms 2.869 ms 2.469 ms
3 89.242.240.1 (89.242.240.1) 34.192 ms 36.496 ms 33.288 ms
4 lg-200-413.rtr001.bre.opaltelecom.net (62.24.252.69) 42.925 ms 31.588 ms 32.567 ms
5 * gig-9-1-rtr001.hex.opaltelecom.net (62.24.254.10) 33.238 ms 33.824 ms
6 gig0-0-rtr002.hex.opaltelecom.net (62.24.196.34) 33.830 ms 32.489 ms 31.438 ms
7 lon.he.net (195.66.226.21) 34.262 ms 52.737 ms 34.409 ms
8 pos4-1.gsr12416.nyc.he.net (216.218.200.101) 193.600 ms 115.531 ms 204.243 ms
9 pos11-0.gsr12416.pao.he.net (216.218.227.225) 189.209 ms 187.628 ms 186.765 ms
10 pos5-0.gsr12416.fmt.he.net (216.218.229.33) 186.706 ms 187.115 ms 209.602 ms
11 216.218.217.182 (216.218.217.182) 186.483 ms 199.948 ms 196.921 ms
12 li3-85.members.linode.com (64.62.190.85) 187.769 ms 187.837 ms 186.804 ms
Update: corrected some spelling |
|
| Back to top |
|
tofu
Joined: 01 Jul 2006
Posts: 29
Location: Ghent, Belgium
|
| Posted: Sat Mar 03, 2007 11:36 am Post subject: |
|
|
tofu wrote: Caker, could you please put a test file on a server in the new datacenter, so I can test the download speed?
I live in Belgium and want to see if I get a higher speed then on host 44 where I am now.
There is not much difference in the ping (now: 126 new DC: 111) http://www.linode.com/forums/viewtopic.php?t=2636 |
|
| Back to top |
|
| |
