Fight the Lag! - with metrics

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

Print
Go Down Pages 1 ... 7 8 9 10 11 ... 18
User actions
June 14, 2012, 07:15:27 PM #200
Lagspike atm.

The request tool seemed a bit laggy too.
Sometimes, severity is the price we pay for greatness
June 14, 2012, 07:52:19 PM #201
The lag is fighting back  Ohgod!
June 14, 2012, 07:54:29 PM #202
3 or 4 minute delays on commands going through


Tracing route to 206.72.207.140 over a maximum of 30 hops

  1     8 ms    21 ms     7 ms  xx.x.xxx.xx
  2    11 ms    11 ms    14 ms  rd1cv-ge3-3-1.gv.shawcable.net [64.59.166.114]
  3    12 ms    15 ms    16 ms  66.163.78.90
  4    29 ms    27 ms    27 ms  66.163.78.174
  5    26 ms    26 ms    27 ms  rc2ar-ge9-2.ed.shawcable.net [66.163.70.9]
  6    49 ms    56 ms    48 ms  66.163.78.138
  7    69 ms    76 ms    69 ms  rc1sh-pos13-0.mt.shawcable.net [66.163.76.73]
  8    80 ms    94 ms    88 ms  rc1hu-pos1-0.ny.shawcable.net [66.163.76.14]
  9    81 ms    77 ms    82 ms  rd1ny-ge5-0-0.ny.shawcable.net [66.163.74.21]
10   150 ms   212 ms   199 ms  198.32.118.45
11    81 ms    77 ms    82 ms  edge-12-teb1.us.as19318.net [64.20.32.78]
12    88 ms   108 ms    94 ms  openvz17.interserver.net [206.72.207.130]
13    92 ms    81 ms    80 ms  206.72.207.140
Quote from: J S BachIf it ain't baroque, don't fix it.
June 14, 2012, 07:58:17 PM #203
This is what the King's Age brings! I say BLAH to it then!
Respect. Responsibility. Compassion.
June 14, 2012, 08:10:22 PM #204
In the grim darkness of the present... there is only lag.
June 14, 2012, 08:14:10 PM #205
Quote from: jstorrie on June 14, 2012, 08:10:22 PM
In the grim darkness of the present... there is only lag.

+1 for the reference.
June 14, 2012, 08:15:43 PM #206 Last Edit: June 14, 2012, 08:30:37 PM by shadeoux
Tracing route to ginka.armageddon.org [206.72.207.140]
over a maximum of 30 hops:


 5    17 ms    31 ms    19 ms  12.249.212.21
 6    18 ms    19 ms    19 ms  cr1.cgcil.ip.att.net [12.122.99.22]
 7    20 ms    12 ms    19 ms  cgcil02jt.ip.att.net [12.122.81.17]
 8    13 ms    17 ms    19 ms  192.205.36.30
 9    13 ms    15 ms    14 ms  xe-1-3-0.cr2.ord2.us.above.net [64.125.30.146]
10   301 ms   234 ms   193 ms  xe-4-0-0.cr2.lga5.us.above.net [64.125.31.73]
11   180 ms    90 ms    36 ms  xe-0-2-1.er2.lga5.us.above.net [64.125.30.210]
12    40 ms    38 ms    37 ms  64.124.44.213.interserver.com [64.124.44.213]
13    40 ms    54 ms    42 ms  edge-12-teb1.us.as19318.net [64.20.32.78]
14    48 ms    37 ms    50 ms  openvz17.interserver.net [206.72.207.130]
15    35 ms    44 ms    37 ms  206.72.207.140

Trace complete.

Two dwarves get into a small fist-fray over who owns a pile of dung at the roadside.

You think:
     "Get your shit together"
June 14, 2012, 08:21:39 PM #207
traceroute to ginka.armageddon.org (206.72.207.140), 64 hops max, 52 byte packets
1  192.168.1.254 (192.168.1.254)  1.758 ms  8.149 ms  1.638 ms
2  d66-183-96-254.bchsia.telus.net (66.183.96.254)  18.148 ms  18.068 ms  9.087 ms
3  173.182.196.1 (173.182.196.1)  9.042 ms  26.282 ms  18.447 ms
4  vancbc01gr01.bb.telus.com (154.11.10.10)  18.977 ms  14.929 ms  12.122 ms
5  205.185.218.69 (205.185.218.69)  11.191 ms  14.831 ms  23.443 ms
6  unknown.hwng.net (209.197.0.249)  94.162 ms  89.995 ms  97.211 ms
7  unknown.hwng.net (209.197.0.38)  122.503 ms  123.367 ms  123.136 ms
8  209.197.17.198 (209.197.17.198)  77.473 ms  83.457 ms  78.888 ms
9  edge-12-teb1.us.as19318.net (64.20.32.78)  79.209 ms
    209.197.17.198 (209.197.17.198)  85.553 ms  91.150 ms
10  edge-12-teb1.us.as19318.net (64.20.32.78)  83.287 ms  85.559 ms  82.648 ms
11  openvz17.interserver.net (206.72.207.130)  88.370 ms  85.054 ms  83.717 ms
12  206.72.207.140 (206.72.207.140)  83.289 ms !Z  91.992 ms !Z  76.097 ms !Z


traceroute to ginka.armageddon.org (206.72.207.140), 64 hops max, 52 byte packets
1  192.168.1.254 (192.168.1.254)  1.758 ms  8.149 ms  1.638 ms
2  d66-183-96-254.bchsia.telus.net (66.183.96.254)  18.148 ms  18.068 ms  9.087 ms
3  173.182.196.1 (173.182.196.1)  9.042 ms  26.282 ms  18.447 ms
4  vancbc01gr01.bb.telus.com (154.11.10.10)  18.977 ms  14.929 ms  12.122 ms
5  205.185.218.69 (205.185.218.69)  11.191 ms  14.831 ms  23.443 ms
6  unknown.hwng.net (209.197.0.249)  94.162 ms  89.995 ms  97.211 ms
7  unknown.hwng.net (209.197.0.38)  122.503 ms  123.367 ms  123.136 ms
8  209.197.17.198 (209.197.17.198)  77.473 ms  83.457 ms  78.888 ms
9  edge-12-teb1.us.as19318.net (64.20.32.78)  79.209 ms
    209.197.17.198 (209.197.17.198)  85.553 ms  91.150 ms
10  edge-12-teb1.us.as19318.net (64.20.32.78)  83.287 ms  85.559 ms  82.648 ms
11  openvz17.interserver.net (206.72.207.130)  88.370 ms  85.054 ms  83.717 ms
12  206.72.207.140 (206.72.207.140)  83.289 ms !Z  91.992 ms !Z  76.097 ms !Z


Experiencing heavy lag in-game.
June 14, 2012, 08:23:24 PM #208
Tracing route to armageddon.org over a maximum of 30 hops:

 1     1 ms     1 ms     1 ms  192.168.1.1
 2    36 ms    31 ms    25 ms  mta-76-176-48-1.san.rr.com [76.176.48.1]
 3     8 ms     8 ms    10 ms  76.166.18.165
 4    37 ms    15 ms    15 ms  tge0-8-0-3.sndhcaax-ccr02.socal.rr.com [72.129.1
.48]
 5    21 ms    23 ms    22 ms  agg22.tustca1-rtr1.socal.rr.com [72.129.1.2]
 6    16 ms    13 ms    15 ms  107.14.19.30
 7    85 ms    81 ms    87 ms  ae-5-0.cr0.dca20.tbone.rr.com [66.109.6.3]
 8    79 ms    78 ms    78 ms  ae-1-0.pr0.dca10.tbone.rr.com [66.109.6.165]
 9    79 ms    79 ms    78 ms  3-3.r1.dc.hwng.net [69.16.190.113]
10   102 ms   111 ms   103 ms  e1-4.r1.ny.hwng.net [209.197.0.34]
11   102 ms   101 ms   118 ms  209.197.17.198
12   100 ms   102 ms   118 ms  edge-12-teb1.us.as19318.net [64.20.32.78]
13   104 ms   101 ms   101 ms  openvz17.interserver.net [206.72.207.130]
14   101 ms   102 ms   103 ms  206.72.207.140

Trace complete.

C:\>
Quote from: Fathi on March 08, 2018, 06:40:45 PMAnd then I sat there going "really? that was it? that's so stupid."

I still think the best closure you get in Armageddon is just moving on to the next character.
June 14, 2012, 08:28:43 PM #209 Last Edit: June 14, 2012, 08:31:37 PM by A Large Bag
Tracing route to 206.72.207.140 over a maximum of 30 hops

 1     1 ms    <1 ms    <1 ms  192.168.1.1
 2     *        *        *     Request timed out.
 3     9 ms     9 ms     8 ms  klsmt001hb6-GE-0-0-0-U144.int.bresnan.net [69.144.26.145]
 4    12 ms    11 ms    12 ms  host-72-175-111-98.bln-mt.client.bresnan.net [72.175.111.98]
 5    14 ms    11 ms    12 ms  mslmt001cr5-GE-3-0-0-U0.int.bresnan.net [72.175.110.5]
 6    28 ms    26 ms    25 ms  klsmt002hb6-SO-0-3-1-U0.int.bresnan.net [69.144.26.2]
 7    27 ms    25 ms    25 ms  blnmtdc1dr5-GE-4-0-3-U0.int.bresnan.net [72.175.110.68]
 8    26 ms    28 ms    28 ms  sesix.r1.se.hwng.net [206.81.80.194]
 9    79 ms    80 ms    84 ms  unknown.hwng.net [209.197.0.249]
10   110 ms   116 ms   112 ms  unknown.hwng.net [209.197.0.38]
11   112 ms   119 ms   124 ms  2-3.r1.ny.hwng.net [69.16.191.93]
12   114 ms   128 ms   115 ms  209.197.17.198
13   113 ms   112 ms   114 ms  edge-12-teb1.us.as19318.net [64.20.32.78]
14   114 ms   114 ms   114 ms  openvz17.interserver.net [206.72.207.130]
15   113 ms   112 ms   114 ms  206.72.207.140

Trace complete.

Lagging just trying to pick selections on the log in screen really bad. Best not to log in at all.
June 14, 2012, 09:33:39 PM #210
How long does it take to fix this kind of thing? I'm not hurrying, I'm just curious...I don't know a whole lot about how the server works and stuffz.
Respect. Responsibility. Compassion.
June 14, 2012, 09:45:01 PM #211
My guess would be a reboot of the server would resolve the issue maybe. But maybe not, it really depends on whats causing the issue. Looks like Local Host though from my estimations. I'd laugh if a virus scan is running now though.
Two dwarves get into a small fist-fray over who owns a pile of dung at the roadside.

You think:
     "Get your shit together"
June 14, 2012, 09:51:48 PM #212
It really really depends on what's wrong. If it's the machine, then it needs someone to reboot it. That means someone at the building where the host server is, needs to be made aware that it's a problem, and needs to be available to do something about it.

If it's not the machine, then it could be the building where the server is hosted (I remember the staff saying it's a virtual machine now - but even so, a virtual machine has to have some link to a real machine, somewhere.) Or it could be a router at a central office in the same town where the virtual server is hosted. Or it could be a satellite dish on the fritz. Or aliens.

In summary, and to reiterate, it depends on what's wrong. Anywhere from "within an hour" to "Arm is broken, thanks for playing, look forward to Halo 4 coming in November." Likely it'll be somewhere between the two.
Talia said: Notice to all: Do not mess with Lizzie's GDB. She will cut you.
Delirium said: Notice to all: do not mess with Lizzie's soap. She will cut you.
June 14, 2012, 09:58:36 PM #213
Lets start killing some aliens! Those bastards are finally trying to get at us.....working from our deepest fears.
Respect. Responsibility. Compassion.
June 14, 2012, 10:18:30 PM #214
1) EST 10:17
2) high sun on cingel the 4th day of the descending sun year 1 of the 22nd age
3) 9, it hasn't booted me yet but it was nearly impossible to connect and I'm experiancing up to a full 30 seconds of lag per command. [not by the server].
June 14, 2012, 10:40:00 PM #215
Geez, this game is broken.
June 14, 2012, 10:45:41 PM #216
Here I was about to log in..            :-[
June 14, 2012, 10:54:13 PM #217
I'm going to try rebooting, please stop trying to log in until I post.  If I can't get it to clear nicely, I may have to bring it down hard.
Morgenes

Producer
Armageddon Staff
June 14, 2012, 10:56:24 PM #218
Quote from: Morgenes on June 14, 2012, 10:54:13 PM
I'm going to try rebooting, please stop trying to log in until I post.  If I can't get it to clear nicely, I may have to bring it down hard.
I got on when it had quickened up for a bit, and now I can't get out again. Sorry Morgenes.  :(
June 14, 2012, 11:30:20 PM #219
Note that we are back up, but even after completely rebooting our entire server, it doesn't seem to have done anything.  I'm opening a trouble ticket with our host to see if they can see/do anything about it.

I apologize, but you may want to find something else to do if you can't handle the lag.
Morgenes

Producer
Armageddon Staff
June 14, 2012, 11:37:41 PM #220
actually, it seems to be working fine atm.
Sometimes, severity is the price we pay for greatness
June 14, 2012, 11:41:07 PM #221
Minor blips but it's fairly quick.
Quote from: Fathi on March 08, 2018, 06:40:45 PMAnd then I sat there going "really? that was it? that's so stupid."

I still think the best closure you get in Armageddon is just moving on to the next character.
June 15, 2012, 01:34:37 AM #222
Lag.

Thu Jun 14 23:33:30 MDT 2012

traceroute to ginka.armageddon.org (206.72.207.140), 64 hops max, 4050 byte packets
1  192.168.1.1 (192.168.1.1)  2.442 ms  2.498 ms  3.078 ms
2  76.120.80.1 (76.120.80.1)  50.122 ms  62.185 ms  180.416 ms
3  te-7-4-ur03.arvada.co.denver.comcast.net (68.86.129.225)  15.444 ms  13.337 ms  19.263 ms
4  te-0-6-0-6-ar02.denver.co.denver.comcast.net (68.86.179.57)  20.608 ms  43.957 ms  19.151 ms
5  pos-0-1-0-0-ar02.aurora.co.denver.comcast.net (68.86.128.242)  21.679 ms  22.701 ms  39.260 ms
6  pos-3-6-0-0-cr01.denver.co.ibone.comcast.net (68.86.91.1)  22.567 ms  22.386 ms  33.099 ms
7  pos-2-7-0-0-cr01.dallas.tx.ibone.comcast.net (68.86.85.54)  35.761 ms  49.735 ms  37.819 ms
8  pos-0-4-0-0-pe01.1950stemmons.tx.ibone.comcast.net (68.86.87.218)  34.720 ms  54.234 ms  35.889 ms
9  xe-5-1-0.er1.dfw2.us.above.net (64.125.13.185)  51.417 ms  55.835 ms  31.911 ms
10  xe-3-1-0.cr1.dfw2.us.above.net (64.125.30.82)  31.540 ms  35.751 ms  34.299 ms
11  xe-2-1-0.cr1.iah1.us.above.net (64.125.30.57)  41.602 ms  39.131 ms  65.552 ms
12  xe-1-0-0.cr2.iah1.us.above.net (64.125.30.70)  58.950 ms  60.535 ms  38.275 ms
13  * xe-3-1-0.cr2.dca2.us.above.net (64.125.30.54)  88.632 ms  99.533 ms
14  xe-3-2-0.cr2.lga5.us.above.net (64.125.26.110)  70.831 ms  86.823 ms  92.413 ms
15  xe-1-0-1.er2.lga5.us.above.net (64.125.26.166)  74.261 ms  70.761 ms  73.413 ms
16  64.124.44.213.interserver.com (64.124.44.213)  87.983 ms  68.689 ms  69.786 ms
17  edge-12-teb1.us.as19318.net (64.20.32.78)  66.960 ms  105.756 ms  90.896 ms
18  openvz17.interserver.net (206.72.207.130)  68.333 ms  71.451 ms  70.086 ms
19  206.72.207.140 (206.72.207.140)  74.633 ms !Z  70.633 ms !Z  69.548 ms !Z
June 15, 2012, 01:35:21 AM #223
*shaking a fist* dang lag!
June 15, 2012, 01:38:05 AM #224
Oh, it's back with a vengeance!
Print
Go Up Pages 1 ... 7 8 9 10 11 ... 18
User actions