Free To Feel

Heading to entrepreneur.

Joshua Chi

Linode Facility Migration to Fremont

After using linode host center at Tokyo for a while, I decided to migrate my node to Fremont.

Linode provide you a speedtest page

Here is my speed testing result. Those two tasks are started at the same time.

100MB-tokyo.bin 1.2/100MB, 47 min left
100MB-fremont.bin 66.5/100MB, 22 secs left

But If I ping the speed test domain:

$ ping
PING ( 56 data bytes
64 bytes from icmp_seq=0 ttl=51 time=82.885 ms
64 bytes from icmp_seq=1 ttl=51 time=77.757 ms
64 bytes from icmp_seq=2 ttl=51 time=77.919 ms

$ ping
PING ( 56 data bytes
64 bytes from icmp_seq=0 ttl=51 time=146.268 ms
Request timeout for icmp_seq 1
64 bytes from icmp_seq=2 ttl=51 time=146.403 ms
64 bytes from icmp_seq=3 ttl=51 time=145.409 ms
64 bytes from icmp_seq=4 ttl=51 time=146.396 ms
64 bytes from icmp_seq=5 ttl=51 time=148.467 ms

As you can see the result is totaly different. So which one you can trust?

The response from linode support:

Individual packets take less time to travel between our Tokyo datacenter and your location than our Fremont datacenter, but that our Fremont datacenter is able to provide you with faster download speeds to your location. Which location is better for you depends on whether your use case likes decreased latency, or better download speeds.

At last I decide to switch to Fremont anyhow. So Linode provide me a new ip address. The interesting thing comes. My ISP blocked this ip address for some reason. You can find the fail point by using either "traceroute" or MTR.

So I asked for a new ip address and reboot my node.

Don't forget to update your hosts file with new ip address to make your application work again. Good luck!

comments powered by Disqus