Fight the Lag! - with metrics

Started by Jeshin, November 17, 2011, 09:00:31 AM

Ok, well if there was lag (not saying it wasn't), it appears to be different, as we aren't seeing the same symptoms in our server side as we were seeing before.
Morgenes

Producer
Armageddon Staff

Just played for 4(ish) hours, didn't have any lag. Think the fix may be working!
*finds a piece of wood to knock on*


Getting lag surges at the moment. It will be fine for a bit and then suddenly lag, fine for a bit, then some lag again. 11:38 EST.
"Life expectancy would grow by leaps and bounds if green vegetables smelled as good as bacon."
~ Doug Larson

"I tried regular hot sauce, but it just wasn't doing the trick, so I started blasting my huevos with BEAR MACE."
~Synthesis

Caught a lag last night for a couple of seconds, but then had a strange and awesome echo.. is the Lag because staff is tinkering with something?
The funny little foreign man

I often hear the jingle to -Riunite on ice- when I read the estate name Reynolte, eve though there ain't no ice in Zalanthas.

Probably important to run tracert's with new lag to confirm whether or not it's system or network lag.

Terrible lag and disconnects for the last quarter of an hour or so. 4pm Gmt, 11am EST I think.

I was having problems also with lag and connectivity.
Quote from: Return of the King (1980)
It's so easy not to try,
Let the world go drifting by--
If you never say, "Hello,"
You won't have to say, "Good Bye."

If you experience a lag, please include a tracert to ginka in your post.  Looking over the last two reports I am unable to correlate it to issues that we were seeing earlier.
Morgenes

Producer
Armageddon Staff

How do you do a traceat to ginka?

Quote from: Booya on December 02, 2011, 02:18:16 PM
How do you do a traceat to ginka?

At your prompt:

> tracert ginka.armageddon.org
Morgenes

Producer
Armageddon Staff

Tried it in my client and and it didn't work.  :-[

Which prompt?

search for cmd.exe if you're using windows.

terminal, on mac.

December 02, 2011, 02:58:21 PM #113 Last Edit: December 02, 2011, 03:05:16 PM by Mazy
I think you confused your mud prompt with command prompt.

Click your window's button (if you're using windows) then go to all programs, and under accessories you should see the command prompt.

Open it and then you can >tracert.

EDIT: Or better yet, do what Delirium said and search for cmd or terminal. After I figured out tracert, I don't think my lag is ginka, because the ginka.armageddon.org is only about ~47 milliseconds. Maybe it's our connections.

EDIT EDIT: My lag is, indeed, on my side. :/
Quote from: Return of the King (1980)
It's so easy not to try,
Let the world go drifting by--
If you never say, "Hello,"
You won't have to say, "Good Bye."

Start > Run > cmd
Quote from: Agameth
Goat porn is not prohibited in the Highlord's city.

Hokay thanks. Next question, is there a way to copy it or do you have to write it out by hand? It won't let me copy the usual ways.


Select all, then copy it. It's a pain but it's the only way.
Quote from: Agameth
Goat porn is not prohibited in the Highlord's city.

3 pm pst, Lag-zilla rears its ugly head.
The funny little foreign man

I often hear the jingle to -Riunite on ice- when I read the estate name Reynolte, eve though there ain't no ice in Zalanthas.

Quote from: Potaje on December 04, 2011, 06:02:37 PM
3 pm pst, Lag-zilla rears its ugly head.

I just went through the logs for the 6pm EST hour yesterday and didn't see anything that would indicate it from our side.  Did you try a tracert?
Morgenes

Producer
Armageddon Staff

Just after midnight, EST, 12-6-11..

The lag beastie cometh.

9:09 pm pst
The funny little foreign man

I often hear the jingle to -Riunite on ice- when I read the estate name Reynolte, eve though there ain't no ice in Zalanthas.

December 06, 2011, 12:11:42 AM #121 Last Edit: December 06, 2011, 12:13:25 AM by drunkendwarf
Right now. Bad.
Mon Dec  5 22:11:25 MST 2011

traceroute to ginka.armageddon.org (209.159.155.236), 64 hops max, 4050 byte packets
1  192.168.1.1 (192.168.1.1)  5.343 ms  2.703 ms  2.421 ms
2  76.120.80.1 (76.120.80.1)  32.083 ms  57.835 ms  191.171 ms
3  te-7-4-ur04.arvada.co.denver.comcast.net (68.86.129.229)  15.402 ms  16.045 ms  36.671 ms
4  te-0-5-0-2-ar02.aurora.co.denver.comcast.net (68.86.179.245)  21.868 ms  27.428 ms  56.031 ms
5  pos-3-7-0-0-cr01.denver.co.ibone.comcast.net (68.86.91.101)  20.886 ms  62.134 ms  26.101 ms
6  pos-2-13-0-0-cr01.dallas.tx.ibone.comcast.net (68.86.86.210)  55.899 ms  93.913 ms  41.234 ms
7  pos-0-5-0-0-pe01.1950stemmons.tx.ibone.comcast.net (68.86.85.26)  54.753 ms  56.067 ms  55.624 ms
8  xe-5-1-0.er1.dfw2.us.above.net (64.125.13.185)  72.030 ms  64.778 ms  32.695 ms
9  xe-1-1-0.cr1.dfw2.us.above.net (64.125.26.209)  39.685 ms  73.747 ms  35.960 ms
10  xe-1-2-0.cr1.iah1.us.above.net (64.125.26.130)  60.250 ms  36.609 ms  57.743 ms
11  xe-0-0-0.cr2.iah1.us.above.net (64.125.30.66)  57.410 ms  62.393 ms  40.342 ms
12  xe-3-1-0.cr2.dca2.us.above.net (64.125.30.54)  71.455 ms  83.809 ms  89.859 ms
13  xe-2-2-0.cr2.lga5.us.above.net (64.125.26.106)  74.189 ms  76.566 ms  73.617 ms
14  xe-0-2-1.er2.lga5.us.above.net (64.125.30.210)  73.449 ms  76.490 ms  77.467 ms
15  64.124.44.213.interserver.com (64.124.44.213)  91.360 ms  91.937 ms  73.715 ms
16  edge-08-teb1.us.as19318.net (64.20.32.9)  89.547 ms  90.358 ms  134.374 ms
17  openvz3.trouble-free.net (64.20.62.226)  491.638 ms  381.069 ms  383.560 ms
18  ginka.armageddon.org (209.159.155.236)  362.043 ms !Z  409.321 ms !Z  409.856 ms !Z


For reference:
traceroute: Warning: www.google.com has multiple addresses; using 74.125.224.112
traceroute to www.l.google.com (74.125.224.112), 64 hops max, 52 byte packets
1  192.168.1.1 (192.168.1.1)  3.829 ms  1.347 ms  1.256 ms
2  76.120.80.1 (76.120.80.1)  42.229 ms  29.677 ms  25.186 ms
te-7-4-ur04.arvada.co.denver.comcast.net (68.86.129.229)  17.089 ms  36.389 ms  70.537 ms
te-0-8-0-1-ar02.aurora.co.denver.comcast.net (68.86.103.41)  19.881 ms  17.565 ms  15.435 ms
pos-3-8-0-0-cr01.denver.co.ibone.comcast.net (68.86.94.153)  16.588 ms  17.204 ms  16.340 ms
pos-2-13-0-0-cr01.dallas.tx.ibone.comcast.net (68.86.86.210)  31.928 ms  30.969 ms  31.923 ms
pos-0-9-0-0-pe01.1950stemmons.tx.ibone.comcast.net (68.86.88.198)  74.116 ms  30.758 ms  31.980 ms
8  75.149.231.70 (75.149.231.70)  88.084 ms  61.496 ms  64.048 ms
9  72.14.233.85 (72.14.233.85)  63.937 ms  62.460 ms
    72.14.233.77 (72.14.233.77)  92.248 ms
10  72.14.237.219 (72.14.237.219)  67.622 ms
    72.14.237.221 (72.14.237.221)  102.098 ms
    72.14.237.215 (72.14.237.215)  65.853 ms
11  64.233.174.142 (64.233.174.142)  86.542 ms  64.705 ms  65.574 ms
12  64.233.174.205 (64.233.174.205)  67.939 ms
    64.233.174.207 (64.233.174.207)  65.938 ms
    64.233.174.205 (64.233.174.205)  112.310 ms
13  209.85.250.65 (209.85.250.65)  71.785 ms  66.648 ms  70.111 ms
14  64.233.174.109 (64.233.174.109)  79.496 ms  65.039 ms  66.751 ms
15  nuq04s08-in-f16.1e100.net (74.125.224.112)  62.508 ms  70.285 ms  136.587 ms

December 06, 2011, 12:12:26 AM #122 Last Edit: December 06, 2011, 12:14:00 AM by JustAnotherGuy
Ran these at 12:10AM EST.  Also getting lag spikes in a constant ping... typically around 150-170ms.  Looks to be Host again.

C:\Users\Knoxx>tracert www.armageddon.org

Tracing route to ginka.armageddon.org [209.159.155.236]
over a maximum of 30 hops:

 1     1 ms    <1 ms     1 ms  192.168.1.1
 2    70 ms    24 ms    22 ms  cpe-173-168-160-1.tampabay.res.rr.com [173.168.1
60.1]
 3    19 ms    13 ms    14 ms  gig12-0-0-2007.tampfledc-rtr2.tampflrdc.rr.com [
65.32.37.38]
 4    11 ms    12 ms    12 ms  653213hfc142.tampabay.res.rr.com [65.32.13.142]

 5    36 ms    37 ms    35 ms  ae-5-10.cr0.dfw10.tbone.rr.com [66.109.6.106]
 6    39 ms    41 ms    69 ms  ae-1-0.pr0.dfw10.tbone.rr.com [66.109.6.179]
 7    36 ms    38 ms    41 ms  ip65-47-204-109.z204-47-65.customer.algx.net [65
.47.204.109]
 8    68 ms    66 ms    71 ms  207.88.14.238.ptr.us.xo.net [207.88.14.238]
 9    70 ms    70 ms    67 ms  vb24.rar3.washington-dc.us.xo.net [207.88.12.34]

10    65 ms   121 ms    63 ms  ae0d0.mcr1.newark-nj.us.xo.net [216.156.0.22]
11    64 ms    69 ms    66 ms  ae1d0.mcr1.nyc-ny.us.xo.net [216.156.1.9]
12   212 ms   207 ms   199 ms  207.239.51.86
13    67 ms    66 ms    67 ms  edge-08-teb1.us.as19318.net [64.20.32.9]
14    66 ms    67 ms    64 ms  openvz3.trouble-free.net [64.20.62.226]
15    64 ms    82 ms    66 ms  ginka.armageddon.org [209.159.155.236]

Trace complete.

C:\Users\Knoxx>tracert www.armageddon.org

Tracing route to ginka.armageddon.org [209.159.155.236]
over a maximum of 30 hops:

 1     1 ms     2 ms     1 ms  192.168.1.1
 2    26 ms    43 ms    30 ms  cpe-173-168-160-1.tampabay.res.rr.com [173.168.1
60.1]
 3    13 ms    30 ms    19 ms  gig12-0-0-2007.tampfledc-rtr2.tampflrdc.rr.com [
65.32.37.38]
 4    14 ms    28 ms    11 ms  653213hfc142.tampabay.res.rr.com [65.32.13.142]

 5    37 ms    37 ms    60 ms  ae-11-11.cr0.dfw10.tbone.rr.com [66.109.10.12]
 6    35 ms    38 ms    34 ms  ae-1-0.pr0.dfw10.tbone.rr.com [66.109.6.179]
 7    41 ms    38 ms    40 ms  ip65-47-204-109.z204-47-65.customer.algx.net [65
.47.204.109]
 8    68 ms    65 ms    66 ms  207.88.14.238.ptr.us.xo.net [207.88.14.238]
 9    70 ms    66 ms    70 ms  vb24.rar3.washington-dc.us.xo.net [207.88.12.34]

10    68 ms    65 ms    69 ms  ae0d0.mcr1.newark-nj.us.xo.net [216.156.0.22]
11    69 ms    64 ms    66 ms  ae1d0.mcr1.nyc-ny.us.xo.net [216.156.1.9]
12    71 ms   203 ms   216 ms  207.239.51.86
13    67 ms    66 ms    68 ms  edge-08-teb1.us.as19318.net [64.20.32.9]
14    66 ms    67 ms    65 ms  openvz3.trouble-free.net [64.20.62.226]
15    66 ms    66 ms    68 ms  ginka.armageddon.org [209.159.155.236]

Trace complete.

Veeeery bad lagspike atm
Sometimes, severity is the price we pay for greatness

Yep, they are coming in spurts...