new datacenter ping test

[console]

Always thought it was something to do with that specific mod since in dm/vanilla there can be 16+ players and it runs perfectly smooth.

However, railz runs the exact same mod binary as vanilla/mutant/dm.

How does your netgraph look when you experience the lag?

[[BTF]Defiant!]

My ping grew by 15-20ms for some reason.  I had an awesome ping of 29 in game, now more like 45.  I shouldn't complain, must be the West Coast route to the server.


ping -n 30 67.228.53.218
Pinging 67.228.53.218 with 32 bytes of data:
Reply from 67.228.53.218: bytes=32 time=69ms TTL=56
Reply from 67.228.53.218: bytes=32 time=70ms TTL=56
Reply from 67.228.53.218: bytes=32 time=80ms TTL=56
Reply from 67.228.53.218: bytes=32 time=131ms TTL=56
Reply from 67.228.53.218: bytes=32 time=91ms TTL=56
Reply from 67.228.53.218: bytes=32 time=52ms TTL=56
Reply from 67.228.53.218: bytes=32 time=68ms TTL=56
Reply from 67.228.53.218: bytes=32 time=81ms TTL=56
Reply from 67.228.53.218: bytes=32 time=74ms TTL=56
Reply from 67.228.53.218: bytes=32 time=46ms TTL=56
Reply from 67.228.53.218: bytes=32 time=51ms TTL=56
Reply from 67.228.53.218: bytes=32 time=60ms TTL=56
Reply from 67.228.53.218: bytes=32 time=58ms TTL=56
Reply from 67.228.53.218: bytes=32 time=67ms TTL=56
Reply from 67.228.53.218: bytes=32 time=70ms TTL=56
Reply from 67.228.53.218: bytes=32 time=69ms TTL=56
Reply from 67.228.53.218: bytes=32 time=78ms TTL=56
Reply from 67.228.53.218: bytes=32 time=94ms TTL=56
Reply from 67.228.53.218: bytes=32 time=71ms TTL=56
Reply from 67.228.53.218: bytes=32 time=77ms TTL=56
Reply from 67.228.53.218: bytes=32 time=68ms TTL=56
Reply from 67.228.53.218: bytes=32 time=48ms TTL=56
Reply from 67.228.53.218: bytes=32 time=84ms TTL=56
Reply from 67.228.53.218: bytes=32 time=48ms TTL=56
Reply from 67.228.53.218: bytes=32 time=58ms TTL=56
Reply from 67.228.53.218: bytes=32 time=46ms TTL=56
Reply from 67.228.53.218: bytes=32 time=51ms TTL=56
Reply from 67.228.53.218: bytes=32 time=55ms TTL=56
Reply from 67.228.53.218: bytes=32 time=47ms TTL=56
Reply from 67.228.53.218: bytes=32 time=58ms TTL=56

Ping statistics for 67.228.53.218:
    Packets: Sent = 30, Received = 30, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 46ms, Maximum = 131ms, Average = 67ms


tracert 67.228.53.218
Tracing route to 67.228.53.218-static.reverse.softlayer.com [67.228.53.218] over a maximum of 30 hops:

  1     2 ms    <1 ms    <1 ms  x.x.x.x LAN/ISP
  2    11 ms    18 ms    52 ms  x.x.x.x LAN/ISP
  3    39 ms    34 ms    23 ms  x.x.x.x LAN/ISP
  4    34 ms    30 ms    22 ms  x.x.x.x LAN/ISP
  5    14 ms    14 ms    26 ms  x.x.x.x LAN/ISP
  6    37 ms    50 ms    41 ms  x.x.x.x LAN/ISP
  7   101 ms   126 ms    94 ms  dls-bb1-link.telia.net [213.248.80.14]
  8    69 ms    62 ms    47 ms  te3-3.bbr02.eq01.dal01.networklayer.com [213.248.102.174]
  9    61 ms    48 ms    50 ms  po6.dar02.sr01.dal01.networklayer.com [173.192.18.213]
 10    46 ms    48 ms   107 ms  po2.fcr03.sr04.dal01.networklayer.com [66.228.118.190]
 11    57 ms    49 ms    51 ms  67.228.53.218-static.reverse.softlayer.com [67.228.53.218]

As far as I know, my ISP does not optimize for ICMP packets, so game performance could be different (actually be better) than ICMP performance.

[Whirlingdervish]

last night mine spiked to 145ms for a good hour on all of the TS texas servers.
I checked my connections to insure that it wasn't something on my end updating, and reset my router and it didn't fix anything.

ran some traceroutes and took a screeny of my netgraph, but they're on my home comp so I'll have to post them later.

my netgraph was showing a green line about .   . that thick with skinny red PL spikes every inch, as opposed to the 2 pixel thick green line I normally see.

I looked over the traceroutes and they were all in order (sub 50ms) until the 3rd hop before I hit tastyspleen. 2 out of the last 3 hops were reporting 145-200ms pings.

some time around 10pm pst it went back to normal, so I just kept playing and didn't get around to complaining