|
 | Server relocation | |
|
|
|
drippy-
Unreasonable Dictator
Hot Roasted
Sniper Delivery
|  | | P: | 10/08/2012 17:24 EST | | E: | 10/11/2012 17:26 EST |
| | |
So I'm not entirely happy with the server where it is right now. I mentioned it in the thread about it, but I had no clue they were going to set it up in Florida; I thought it was going to be in NJ.
For the majority of players, this adds some latency. Its still pretty reasonable for TFC, but I also see some disconnects and lag spikes that seem to be network related at this host. Also, I can't seem to push a lot of data from the server itself (it seems to be capped artificially at 1MB/sec, despite claiming a 100Mb port) - inconsequential to the game server but indicating a sub-par network.
To that end, I've been looking into other hosts, but not coming up with a perfect solution. These are hosts that offer a better or comparable deal on the server itself... I would prefer a central or eastern US location (my current choice is host 1), but these are still better than Florida.
So, for those that know how and care, could you ping these and tell me if the latency is acceptable to you?
Host 1: 96.43.134.146 (Kansas City, MO)
Host 2: 66.171.176.15 (Seattle)
Host 3: 64.56.64.1 (LA)
Edit: None of those look good...
Host 4: 76.73.4.5 (Denver)
Host 5: 108.61.74.131 (NY)
Host 6: 69.50.217.209 (AZ)
Host 7: 199.189.248.77 (Atlanta)
| |
|
|
angry_salad
Super Regular
Medic Capping
Service
| | | P: | 10/08/2012 17:39 EST |
| | |
Best & worst (from Toronto)
KC:
Reply from 96.43.134.146: bytes=32 time=44ms TTL=53
Reply from 96.43.134.146: bytes=32 time=47ms TTL=53
WA:
Reply from 66.171.176.15: bytes=32 time=77ms TTL=242
Reply from 66.171.176.15: bytes=32 time=82ms TTL=242
LA:
Reply from 64.56.64.1: bytes=32 time=104ms TTL=242
Reply from 64.56.64.1: bytes=32 time=103ms TTL=242
Current:
Reply from 199.193.114.171: bytes=32 time=66ms TTL=54
Reply from 199.193.114.171: bytes=32 time=65ms TTL=54 | |
|
|
purg3d
Peon
Medic
| | P: | 10/08/2012 17:45 EST |
| | |
Host 1: 96.43.134.146 (Kansas City, MO) -57ms
Host 2: 66.171.176.15 (Seattle) -93ms
Host 3: 64.56.64.1 (LA) -84ms
Current Host: -50ms
| |
|
|
|
| | |
KC=24ms,50
Seattle 64ms,240
LA 86ms,242 | |
|
|
|
| | |
if someone shows me how, I'll post mine too | |
|
|
|
| | |
KC:
Reply from 96.43.134.146: bytes=32 time=44ms TTL=54
Reply from 96.43.134.146: bytes=32 time=43ms TTL=54
WA:
Reply from 66.171.176.15: bytes=32 time=86ms TTL=243
Reply from 66.171.176.15: bytes=32 time=89ms TTL=243
LA:
Reply from 64.56.64.1: bytes=32 time=74ms TTL=241
Reply from 64.56.64.1: bytes=32 time=89ms TTL=241
To ping:
Step 1: Open your command prompt (either type "cmd" into your start menu, or go to Start Menu -> All Programs -> Accessories -> Command Prompt)
Step 2: On any line, type ping ***.***.***.***, where the stars are the IP address (not all three stars are necessarily used in each triplet).
Step 3: It's actually tricky to copy/paste, at least from windows command prompt. First, right click and select "mark." This allows you to click and drag to select text. To copy that text, instead of the regular "Ctrl-C" ... just press enter (which also removes your "mark"). Now you should be able to Ctrl-V (paste) into your browser or wherever. | |
|
|
DeathBringer
Super Regular
Pipey FlagCatcher
| | | P: | 10/08/2012 19:05 EST | | E: | 10/08/2012 19:10 EST |
| | |
Kansas city Mo is the lowest for me @ 61. But im in NW kansas.
Currently i get a 68 on the FL server.
I think the gas chamber server is in Tx and i get a 30-35 latency there.
KC = 61
Seattle = 105
LA = 85 | |
|
|
angry_salad
Super Regular
Medic Capping
Service
| | | P: | 10/08/2012 20:18 EST |
| | |
 | I Can |3ean You wrote:
Step 3: It's actually tricky to copy/paste, | |
ping 96.43.134.146 > d:\kc_result.txt
Outputs to a text file at the specified path.
| |
|
|
B|ind Sniper
Daycare Manager
WMD Creator
| | | P: | 10/08/2012 20:26 EST |
| | |
Kansas City is good 4 me! 46ms | |
|
|
Errorist
Super Regular
Dizzy Capper
| | P: | 10/08/2012 21:08 EST |
| | |
Kansas City:
Reply from 96.43.134.146: bytes=32 time=44ms TTL=48
Reply from 96.43.134.146: bytes=32 time=33ms TTL=48
Seattle:
Reply from 66.171.176.15: bytes=32 time=79ms TTL=235
Reply from 66.171.176.15: bytes=32 time=81ms TTL=235
Los Angeles:
Reply from 64.56.64.1: bytes=32 time=76ms TTL=241
Reply from 64.56.64.1: bytes=32 time=76ms TTL=241
| |
|
|
epz
Super Regular
Dizzy Capper
| | | P: | 10/08/2012 21:27 EST |
| | |
KC:
Reply from 96.43.134.146: bytes=32 time=39ms TTL=52
Reply from 96.43.134.146: bytes=32 time=40ms TTL=52
Seattle:
Reply from 66.171.176.15: bytes=32 time=85ms TTL=236
Reply from 66.171.176.15: bytes=32 time=84ms TTL=236
LA:
Reply from 64.56.64.1: bytes=32 time=74ms TTL=245
Reply from 64.56.64.1: bytes=32 time=75ms TTL=245 | |
|
|
|
| | |
It looks like, among those three choices, Kansas City is the consistent winner. | |
|
|
MuadDib
Super Regular
Medic Capping
Service
| | | P: | 10/08/2012 21:37 EST | | E: | 10/08/2012 22:13 EST |
| | |
KC: Pinging 96.43.134.146 with 32 bytes of data:
Reply from 96.43.134.146: bytes=32 time=70ms TTL=49
Reply from 96.43.134.146: bytes=32 time=68ms TTL=49
Reply from 96.43.134.146: bytes=32 time=68ms TTL=49
Reply from 96.43.134.146: bytes=32 time=69ms TTL=49
Ping statistics for 96.43.134.146:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 68ms, Maximum = 70ms, Average = 68ms
WA: Pinging 66.171.176.15 with 32 bytes of data:
Reply from 66.171.176.15: bytes=32 time=87ms TTL=242
Reply from 66.171.176.15: bytes=32 time=87ms TTL=242
Reply from 66.171.176.15: bytes=32 time=88ms TTL=242
Reply from 66.171.176.15: bytes=32 time=87ms TTL=242
ping statistics for 66.171.176.15:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 87ms, Maximum = 88ms, Average = 87ms
LA: Pinging 64.56.64.1 with 32 bytes of data:
Reply from 64.56.64.1: bytes=32 time=97ms TTL=243
Reply from 64.56.64.1: bytes=32 time=96ms TTL=243
Reply from 64.56.64.1: bytes=32 time=97ms TTL=243
Reply from 64.56.64.1: bytes=32 time=101ms TTL=243
Ping statistics for 64.56.64.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Minimum = 96ms, Maximum = 101ms, Average = 97ms
Drippy- wrote: So, for those that know how and care, could you ping these and tell me if the latency is acceptable to you?
MuadDib is adaptable… all 3 potential locations are acceptable to me
| |
|
|
Rand
Super Regular
Rocket Jumping
Capper
| | P: | 10/08/2012 21:55 EST |
| | |
Pinging 96.43.134.146 with 32 bytes of data:
Reply from 96.43.134.146: bytes=32 time=44ms TTL=49
Reply from 96.43.134.146: bytes=32 time=44ms TTL=49
Reply from 96.43.134.146: bytes=32 time=43ms TTL=49
Reply from 96.43.134.146: bytes=32 time=43ms TTL=49
Ping statistics for 96.43.134.146:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 43ms, Maximum = 44ms, Average = 43ms
Pinging 66.171.176.15 with 32 bytes of data:
Reply from 66.171.176.15: bytes=32 time=65ms TTL=242
Reply from 66.171.176.15: bytes=32 time=66ms TTL=242
Reply from 66.171.176.15: bytes=32 time=64ms TTL=242
Reply from 66.171.176.15: bytes=32 time=62ms TTL=242
Ping statistics for 66.171.176.15:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 62ms, Maximum = 66ms, Average = 64ms
Pinging 64.56.64.1 with 32 bytes of data:
Reply from 64.56.64.1: bytes=32 time=79ms TTL=242
Reply from 64.56.64.1: bytes=32 time=82ms TTL=242
Reply from 64.56.64.1: bytes=32 time=96ms TTL=242
Reply from 64.56.64.1: bytes=32 time=93ms TTL=242
Ping statistics for 64.56.64.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 79ms, Maximum = 96ms, Average = 87ms
Pinging 199.193.114.171 with 32 bytes of data:
Reply from 199.193.114.171: bytes=32 time=54ms TTL=51
Reply from 199.193.114.171: bytes=32 time=53ms TTL=51
Reply from 199.193.114.171: bytes=32 time=53ms TTL=51
Reply from 199.193.114.171: bytes=32 time=52ms TTL=51
Ping statistics for 199.193.114.171:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 52ms, Maximum = 54ms, Average = 53ms | |
|
|
|
| | |
KC - 67ms
WA - 88ms
LA - 98ms
Current - 64ms
I get the lowest (although not all that much better than KC) with the current server but I do get a lot of lag spikes on the current server. I'm also not sure if it's me but I also connect a lot and it's really choppy, sometimes I have to do a retry a couple of times to get it to go away, sometimes oddly enough, alt-tabbing out and back in makes it work. The alt-tabbing solution leads me to believe that's a client side issue though. But regardless, I've seen more lag spikes from the whole server with the current server than wherever it was after it was since Montreal. IIRC, there was a server in between the time in Montreal and Florida? | |
|
|
|
| Forums > D2F Discussion (Archives) > Server relocation |
