ok sine....here are some traceroutes:LEGAL DISCLAIMER: Traceroutes can be VERY misleading, and only tell part of the story. To fully understand how two servers interact, you have to know who their networking providers are! However, I do know who the networking providers are for each of the servers that I am posting a traceroute from and understand the problems, etc. So, I am taking the time to write a book, for not only your sake, but in the hopes that the community will chill! Please understand, I am constantly re-evaluting my VPS providers, and changing VPS providers as needed. For instance, I have just picked up a NYC based VPS that is hosting this server: TheServerPharmNY: Fortress Freedom! I am trying this service out to see if i can improve upon the performance that i currently get with my Chicago VPS. I am also considering dropping my Atlanta VPS and moving what I have there to NYC.
OK, here is the structure of the series of test that I am showing you in this post. I have a VPS that is hosted in the UK. This VPS has provem itself to be a great performer. I will be marketing server slots there. I will run a traceroute from the VPS on Wild West's dedicated server. I will run a traceroute from my Chicago server. I will run a traceroute from my NYC server. Please understand that such traceroutes have are being run between data centers. So, they eliminate the "last mile" that would get to a person's house. The benefit of such a traceroute combined with a knowledge of the networking providers, is thus. It exposes the "underlying structure" of how a given server may connect to someone in said city. It is particularly useful in this scenario because each of these datacenters is very close to an AT&T routing center. AT&T routing centers process 97% of all internet traffic in the USA.
The 1st traceroute is from my Chicago server to my UK server.
compguygene@thserver:~$ traceroute 115.124.117.180
traceroute to 115.124.117.180 (115.124.117.180), 30 hops max, 40 byte packets
1 . (66.90.101.41) 0.037 ms 0.011 ms 0.010 ms
2 75.149.229.81 (75.149.229.81) 1.088 ms 1.064 ms 1.045 ms
3 pos-1-3-0-0-cr01.chicago.il.ibone.comcast.net (68.86.86.33) 1.967 ms 1.950 ms 1.932 ms
4 xe-2-1-0.chi10.ip.tiscali.net (77.67.68.37) 0.927 ms 0.897 ms 0.869 ms
5 xe-10-2-0.lon20.ip.tiscali.net (89.149.185.210) 111.744 ms 111.725 ms xe-10-3-0.lon20.ip.tiscali.net (89.149.184.45) 111.677 ms
6 blueconnex-gw.ip.tiscali.net (77.67.67.138) 111.681 ms 111.612 ms 112.576 ms
7 pri.the-hex.as29550.net (92.48.95.10) 111.544 ms 111.845 ms 111.755 ms
8 pri.bsq3-the.as29550.net (217.112.81.90) 116.719 ms 121.695 ms 121.684 ms
9 94-76-201-90.static.as29550.net (94.76.201.90) 112.678 ms 112.658 ms 111.634 ms
10 115.124.117.180 (115.124.117.180) 112.610 ms 112.240 ms 113.192 ms
People who live in the UK typically ping in the 125ms to 135ms range when using my Chicago server. The company that hosts both servers in this traceroute use the same internet networking providers. And the networking providers are the most commonly used providers by ISP's.
The next traceroute is from my Ww VPS in Texas.
compguygene@compguygene:~$ traceroute 115.124.117.180
traceroute to 115.124.117.180 (115.124.117.180), 30 hops max, 40 byte packets
1 66.71.249.194 (66.71.249.194) 0.055 ms 0.012 ms 0.013 ms
2 core-a-g5-7.atl.wiresix.net (66.71.255.13) 0.815 ms 0.809 ms 0.809 ms
3 wiresix-atl-core-h-p0-1.gnax.net (207.210.92.133) 0.770 ms 0.761 ms 0.748 ms
4 xe1-2.cr01.atl01.mzima.net (67.199.136.157) 13.466 ms 13.462 ms 13.449 ms
5 te1-7.cr01.iad01.us.mzima.net (69.174.120.54) 15.038 ms 15.025 ms 15.012 ms
6 te4-4.cr01.lga01.us.mzima.net (69.174.120.61) 28.716 ms 19.471 ms 19.446 ms
7 xe0-0.cr01.lga02.us.mzima.net (216.193.255.214) 18.934 ms 27.388 ms 27.360 ms
8 eos3-1.cr01.lhr01.uk.mzima.net (216.193.255.178) 98.881 ms eos2-0.cr01.lhr01.uk.mzima.net (216.193.255.46) 98.871 ms 98.858 ms
9 the-linx.blueconnex.net (195.66.224.223) 94.836 ms 94.814 ms 94.777 ms
10 pri.bsq3-the.as29550.net (217.112.81.90) 96.163 ms 96.493 ms 96.135 ms
11 94-76-201-90.static.as29550.net (94.76.201.90) 95.456 ms 95.447 ms 95.521 ms
12 115.124.117.180 (115.124.117.180) 95.512 ms 95.485 ms 95.953 ms
Two things should be noted on this traceroute. First, it is very misleading. Because Wild West's dedicated server uses a very good backbone...it is particularly good at server to server routes. But note network hops 4-8. That mzima.net is a common provider for "West of the Mississippi". However, the company in question is rarely a provider for East Coast or Euro companies. And none of my other VPS providers use this company for an Network provider. The reason that "West of the Mississippi" companies use this company is that they are one of the absolute best providers in that part of the USA. Manta has informed me that his provider is in negotiations with an additional provider that would link up better with the rest of the world. And said provider is used by each of my other VPS providers.
The third traceroute is from my NYC VPS to my UK VPS.
compguygene@TheServerPharmNYarma:~$ traceroute 115.124.117.180
traceroute to 115.124.117.180 (115.124.117.180), 30 hops max, 40 byte packets
1 216.66.73.65 (216.66.73.65) 0.231 ms 0.258 ms 0.320 ms
2 10gigabitethernet2-4.core1.nyc4.he.net (72.52.92.101) 22.070 ms 22.125 ms 22.181 ms
3 10gigabitethernet1-2.core1.lon1.he.net (72.52.92.78) 91.096 ms 91.133 ms 91.190 ms
4 the-linx.blueconnex.net (195.66.224.223) 91.259 ms 91.297 ms 91.340 ms
5 pri.bsq3-the.as29550.net (217.112.81.90) 94.445 ms 94.550 ms 94.677 ms
6 94-76-201-90.static.as29550.net (94.76.201.90) 92.038 ms 91.997 ms 92.031 ms
7 115.124.117.180 (115.124.117.180) 92.104 ms 92.097 ms 92.085 ms
Now you see why I am so hot to get a VPS in NYC! Such a VPS may be ideal for Euro-American interaction. If the server I have put up load tests well. I will list that server for the July Ladle. Initial tests last night with Hoop and a few other Euros have shown that it may be a good performer. But much more gameplay needs to happen before I will entrust my servers to it.
At this point i would like to point out the page on the wiki that refers to lag
http://wiki.armagetronad.net/index.php?title=Lag I would like to point out one more issue that the wiki page does not address. During peak usage times of internet use, all bets are off as to the performance of a given game server. It's because of your ISP, not the server. For example, I switched from DSL to cable, because the phone company was rather slow upgrading to a decent sized network pipe. However, you must understand the fundamental advantage of DSL to cable. DSL is a GUARANTEED connection between you and the phone company. You do not share that connection with anyone else. Cable is a shared service of however many households are on the same fiber-optic port at the fiber optic switch your connected to. And many Saturday nights, as more people in my town have gotten Cable Internet, my access sucks. Recently, the phone company upgraded the DSL, so I am going to switch back.
I hope this posts exposes in an understandable manner the underlying networking issues.