Network performance tests

Sim

Sim

Administrator
I'm hoping that I can get a few people to help me with some network performance tests - I'm trying to work out where to locate a new server for some of my websites. I've narrowed it down to a choice between Fremont (California) or Tokyo (unfortunately, Australia isn't an option just yet).

My testing indicates that Tokyo gives far better performance - but my ISP is Internode, which I know has direct international network links to Japan, so I'm not sure if I'm getting representative results for other Australian internet users.

Some things I'm curious about are, response times, number of network hops, (and download speed - but that's a little more difficult to test consistently).

I'm looking for a few people with ADSL2+ (or better) connections, on ISPs other than Internode to try the following commands (assuming you're using Windows):

ping fremont1.linode.com
tracert fremont1.linode.com

ping tokyo1.linode.com
tracert tokyo1.linode.com

... and paste the results into a reply here. In particular, I want to see the average round trip time (ms) from ping, and the number of hops from tracert ... and which ISP you're using!

If you're more technically inclined and would like to do some speed tests for me, I'd also love to see an average transfer rate as calculated by wget (Linux users might already have this installed, Windows users can download a command line version from http://downloads.sourceforge.net/gnuwin32/wget-1.11.4-1-setup.exe ... when installed, just type wget with the URL as a parameter - as per below).

Here are the files I'd like you to test (both 100MB in size):

wget http://fremont1.linode.com/100MB-fremont.bin
wget http://tokyo1.linode.com/100MB-tokyo.bin

I specify wget, because that's the tool I've been using for testing - I figured it would be best to use the same tool for consistency. I'm looking for an average transfer rate (in kB/s) as reported by wget once the transfer has completed.

The actual speed isn't as important (ie if you have a really fast or slow link) as the comparison between the two sites - Fremont and Tokyo.

If you don't understand a word of this post, then don't worry about it - just go read something more interesting about real estate and ignore this :D
 
I've just been recommended getting a linode in Japan for a .au site so could you be a dear and share your results when you get them? :D

I'm on internode too so can't help with the testing.
 
Telstra wireless broadband

Telstra wireless broadband approx 1/2Mbs[sup]-1[/sup] in the end of nowhere threeways NT,

Pinging fremont1.linode.com [64.71.152.17] with 32 bytes of data:
Reply from 64.71.152.17: bytes=32 time=856ms TTL=49
Reply from 64.71.152.17: bytes=32 time=873ms TTL=49
Reply from 64.71.152.17: bytes=32 time=897ms TTL=49
Reply from 64.71.152.17: bytes=32 time=921ms TTL=49
Ping statistics for 64.71.152.17:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 856ms, Maximum = 921ms, Average = 886ms

Tracing route to fremont1.linode.com [64.71.152.17]
over a maximum of 30 hops:
1 4 ms 1 ms 1 ms 192.168.0.1
2 750 ms 481 ms 1053 ms 10.4.149.195
3 * * * Request timed out.
4 * * * Request timed out.
5 * * * Request timed out.
6 * * * Request timed out.
7 * * * Request timed out.
8 * * * Request timed out.
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 1039 ms 1023 ms 572 ms fremont1.linode.com [64.71.152.17]
Trace complete.

Pinging tokyo1.linode.com [106.187.33.12] with 32 bytes of data:
Reply from 106.187.33.12: bytes=32 time=499ms TTL=49
Reply from 106.187.33.12: bytes=32 time=516ms TTL=49
Reply from 106.187.33.12: bytes=32 time=539ms TTL=49
Reply from 106.187.33.12: bytes=32 time=563ms TTL=49
Ping statistics for 106.187.33.12:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 499ms, Maximum = 563ms, Average = 529ms

Tracing route to tokyo1.linode.com [106.187.33.12]
over a maximum of 30 hops:
1 3 ms 2 ms 1 ms 192.168.0.1
2 139 ms 119 ms 109 ms 10.4.149.195
3 * * * Request timed out.
4 * * * Request timed out.
5 * * * Request timed out.
6 * * * Request timed out.
7 * * * Request timed out.
8 * * * Request timed out.
9 * * * Request timed out.
10 * * * Request timed out.
11 * * * Request timed out.
12 * * * Request timed out.
13 * * * Request timed out.
14 * * * Request timed out.
15 * * * Request timed out.
16 397 ms 510 ms 511 ms tokyo1.linode.com [106.187.33.12]
Trace complete.


Tokyo
 
Tpg adsl2+

Pinging fremont1.linode.com [64.71.152.17] with 32 bytes of data:
Reply from 64.71.152.17: bytes=32 time=181ms TTL=56
Reply from 64.71.152.17: bytes=32 time=180ms TTL=56
Reply from 64.71.152.17: bytes=32 time=181ms TTL=56
Reply from 64.71.152.17: bytes=32 time=180ms TTL=56

Ping statistics for 64.71.152.17:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 180ms, Maximum = 181ms, Average = 180ms


Tracing route to fremont1.linode.com [64.71.152.17]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.1
2 17 ms 17 ms 16 ms 10.20.20.187
3 146 ms 21 ms 17 ms nme-sot-dry-csw1-te-4-3.tpgi.com.au 203.12.162.249]
4 16 ms 15 ms 16 ms nme-sot-dry-crt1-ge-0-0-0.tpgi.com.au [202.7.171.113]
5 17 ms 16 ms 16 ms nme-nxg-wal-crt1-ge-5-0-0.tpgi.com.au [202.7.162.45]
6 28 ms 28 ms 28 ms syd-nxg-men-crt1-ge-3-1-0.tpgi.com.au [202.7.173.241]
7 177 ms 177 ms 177 ms 207.114.154.9
8 179 ms 178 ms 194 ms sjc1-pr1-xe-1-3-0-0.us.twtelecom.net [66.192.249.26]
9 181 ms 180 ms 192 ms 10.123.123.1
10 182 ms 180 ms 180 ms linode-llc.10gigabitethernet2-3.core1.fmt1.he.net [64.62.250.6]
11 180 ms 181 ms 180 ms fremont1.linode.com [64.71.152.17]

Trace complete.


Pinging tokyo1.linode.com [106.187.33.12] with 32 bytes of data:
Reply from 106.187.33.12: bytes=32 time=131ms TTL=54
Reply from 106.187.33.12: bytes=32 time=140ms TTL=54
Reply from 106.187.33.12: bytes=32 time=130ms TTL=54
Reply from 106.187.33.12: bytes=32 time=130ms TTL=54

Ping statistics for 106.187.33.12:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 130ms, Maximum = 140ms, Average = 132ms

Tracing route to tokyo1.linode.com [106.187.33.12]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms 192.168.1.1
2 16 ms 16 ms 16 ms 10.20.20.187
3 17 ms 16 ms 16 ms nme-sot-dry-csw2-te-4-3.tpgi.com.au [203.12.162.253]
4 17 ms 17 ms 16 ms nme-sot-dry-crt1-ge-0-1-0.tpgi.com.au [202.7.173.49]
5 28 ms 28 ms 28 ms syd-sot-ken-crt4-Te-2-0-0.tpgi.com.au [203.29.135.245]
6 128 ms 129 ms 128 ms ix-11-1-0-507.tcore2.TV2-Tokyo.as6453.net [116.0.88.21]
7 130 ms 205 ms 200 ms if-1-0-0-1715.core1.TV2-Tokyo.as6453.net [209.58.61.125]
8 128 ms 141 ms 128 ms Vlan10.ihar1.OVC-Tokyo.as6453.net [209.58.61.158]
9 140 ms 128 ms 140 ms 118.155.194.61
10 129 ms 128 ms 130 ms otejbb204.kddnet.ad.jp [59.128.7.194]
11 138 ms 144 ms 143 ms cm-fcu203.kddnet.ad.jp [124.215.194.180]
12 130 ms 129 ms 132 ms 124.215.199.122
13 130 ms 131 ms 130 ms tokyo1.linode.com [106.187.33.12]
 
Last edited:
Thanks everyone - so it looks like both Telstra and TPG seem to like Japan as a destination so far.

I've just finished migrating some of my internal websites previously hosted in Australia to the new Tokyo server (helpdesk, project management system, etc) ... performance is really good so far (ie no network issues).

RumpledElf said:
I've just been recommended getting a linode in Japan for a .au site so could you be a dear and share your results when you get them?
Click to expand...

Would be glad to.

Loving Linode so far ... I've now got three Linode servers running ... one 768 in Newark, NJ (main audience is in US & UK, hence the location choice ... just had to upgrade it the other day - it's getting hammered!), plus two 512s in Tokyo (one production server I'm just running up now, plus one dev/test for playing on).
 
Pinging fremont1.linode.com [64.71.152.17] with 32 bytes of data:

Reply from 64.71.152.17: bytes=32 time=241ms TTL=49
Reply from 64.71.152.17: bytes=32 time=251ms TTL=49
Reply from 64.71.152.17: bytes=32 time=259ms TTL=49
Reply from 64.71.152.17: bytes=32 time=237ms TTL=49

Ping statistics for 64.71.152.17:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 237ms, Maximum = 259ms, Average = 247ms
------------

Pinging tokyo1.linode.com [106.187.33.12] with 32 bytes of data:

Reply from 106.187.33.12: bytes=32 time=154ms TTL=48
Reply from 106.187.33.12: bytes=32 time=151ms TTL=48
Reply from 106.187.33.12: bytes=32 time=153ms TTL=48
Reply from 106.187.33.12: bytes=32 time=153ms TTL=48

Ping statistics for 106.187.33.12:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 151ms, Maximum = 154ms, Average = 152ms

-------------------
Both tracerts time out

http://fremont1.linode.com/100MB-fremont.bin ~300kBs

http://tokyo1.linode.com/100MB-tokyo.bin ~145kBs

Hostgator ~140kBs

Hostgator* is best value for small stuff although I have done 20-40G of data per mth for a while now.
I also use hostway & amazon.

1458782994.png


*edit corrected
 
Last edited:
On TPG

C:\WINDOWS>ping fremont1.linode.com

Pinging fremont1.linode.com [64.71.152.17] with 32 bytes of data:

Reply from 64.71.152.17: bytes=32 time=173ms TTL=56
Reply from 64.71.152.17: bytes=32 time=172ms TTL=56
Reply from 64.71.152.17: bytes=32 time=171ms TTL=56
Reply from 64.71.152.17: bytes=32 time=171ms TTL=56

Ping statistics for 64.71.152.17:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 171ms, Maximum = 173ms, Average = 171ms

C:\WINDOWS>tracert fremont1.linode.com

Tracing route to fremont1.linode.com [64.71.152.17]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms home.gateway [192.168.42.254]
2 9 ms 10 ms 10 ms syd-pow-cla-bras-13-lo-20.tpgi.com.au [10.20.21.
180]
3 10 ms 10 ms 15 ms syd-pow-cla-csw-2-po-16.tpgi.com.au [202.7.173.1
3]
4 10 ms 9 ms 9 ms syd-pow-cla-crt2-ge-4-0.tpgi.com.au [202.7.162.9
]
5 151 ms 152 ms 151 ms 97.65.99.17
6 155 ms 155 ms 155 ms sea2-pr2-xe-1-3-0-0.us.twtelecom.net [66.192.253.122]
7 172 ms 175 ms 172 ms 10gigabitethernet9-1.core1.sjc2.he.net [72.52.92.157]
8 174 ms 174 ms 175 ms 10.123.123.1
9 173 ms 172 ms 172 ms linode-llc.10gigabitethernet2-3.core1.fmt1.he.net [64.62.250.6]
10 171 ms 172 ms 195 ms fremont1.linode.com [64.71.152.17]

Trace complete.


C:\WINDOWS>ping tokyo1.linode.com

Pinging tokyo1.linode.com [106.187.33.12] with 32 bytes of data:

Reply from 106.187.33.12: bytes=32 time=111ms TTL=54
Reply from 106.187.33.12: bytes=32 time=112ms TTL=54
Reply from 106.187.33.12: bytes=32 time=112ms TTL=54
Reply from 106.187.33.12: bytes=32 time=112ms TTL=54

Ping statistics for 106.187.33.12:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 111ms, Maximum = 112ms, Average = 111ms

C:\WINDOWS>tracert tokyo1.linode.com

Tracing route to tokyo1.linode.com [106.187.33.12]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms home.gateway [192.168.42.254]
2 9 ms 8 ms 9 ms syd-pow-cla-bras-13-lo-20.tpgi.com.au [10.20.21.180]
3 10 ms 9 ms 10 ms syd-pow-cla-csw-1-po-15.tpgi.com.au [202.7.173.9]
4 10 ms 10 ms 9 ms syd-pow-cla-crt1-ge-7-0.tpgi.com.au [202.7.162.1
41]
5 9 ms 9 ms 9 ms syd-sot-ken-crt-4-Ten-9-1.tpgi.com.au [203.29.135.157]
6 10 ms 9 ms 10 ms syd-sot-ken-crt-4-Ten-9-1.tpgi.com.au [203.29.135.157]
7 120 ms 109 ms 110 ms ix-11-1-0-507.tcore2.TV2-Tokyo.as6453.net [116.0.88.21]
8 110 ms 110 ms 111 ms if-1-0-0-1715.core1.TV2-Tokyo.as6453.net [209.58.61.125]
9 112 ms 110 ms 122 ms Vlan10.ihar1.OVC-Tokyo.as6453.net [209.58.61.158]
10 113 ms 109 ms 109 ms 118.155.194.61
11 111 ms 110 ms 110 ms otejbb203.kddnet.ad.jp [59.128.7.129]
12 113 ms 111 ms 121 ms cm-fcu203.kddnet.ad.jp [124.215.194.164]
13 118 ms 111 ms 112 ms 124.215.199.122
14 111 ms 111 ms 112 ms tokyo1.linode.com [106.187.33.12]

Trace complete.
jason@pegasus:~$ wget http://fremont1.linode.com/100MB-fremont.bin
--2011-12-03 07:17:31-- http://fremont1.linode.com/100MB-fremont.bin
Resolving fremont1.linode.com... 64.71.152.17
Connecting to fremont1.linode.com|64.71.152.17|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 104857600 (100M) [application/octet-stream]
Saving to: '100MB-fremont.bin.1'

100%[======================================>] 104,857,600 1.12M/s in 1m 48s

2011-12-03 07:19:19 (949 KB/s) - '100MB-fremont.bin.1' saved [104857600/104857600]


jason@pegasus:~$ wget http://tokyo1.linode.com/100MB-tokyo.bin
--2011-12-03 07:19:51-- http://tokyo1.linode.com/100MB-tokyo.bin
Resolving tokyo1.linode.com... 106.187.33.12
Connecting to tokyo1.linode.com|106.187.33.12|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 104857600 (100M) [application/octet-stream]
Saving to: '100MB-tokyo.bin'

100%[======================================>] 104,857,600 731K/s in 97s

2011-12-03 07:21:29 (1.03 MB/s) - '100MB-tokyo.bin' saved [104857600/104857600]
 
Last edited:
I don't know if this is related but in recent days whenever I click on anything on SS there is a delay and I get the "waiting for SS" notification.

Just though I would mention it
 
Dunno if its the hosting or vBulletin but this goes regularly goes into sleep mode.
I do have a vB site doing 4-8Gig a mth which doesn't have that problem.

PS my hostway plan is $500 mth and amazon cloud hosting is >2k mth, that is two thousand $$ per mth. I know something about this stuff.
 
You must log in or register to reply here.
Back
Top