Fight the Lag! - with metrics

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

Print
Go Down Pages 1 ... 16 17 18
User actions
April 30, 2013, 08:37:52 PM #425
How do I obtain metrics again? ..I use atlantis?  :-[

EDIT: ^ I love you Delirium for using hexxus in this thread to represent lag
I have learned that one can, in fact, typo to death.

Quote from: KismeticTuluk is not Inception, the text experience.
April 30, 2013, 08:39:31 PM #426 Last Edit: February 20, 2023, 12:58:05 PM by Barsook
Code Select
traceroute to armageddon.org (209.159.155.76), 30 hops max, 60 byte packets
1  unknown (192.168.1.1)  1.228 ms  1.171 ms  1.630 ms
2  * * *
3  ae0-1031.cr02.dytnoh55.swo.rr.com (184.59.244.116)  23.962 ms  24.722 ms  24.708 ms
4  network-065-029-001-046.midwest.rr.com (65.29.1.46)  34.825 ms  34.858 ms  34.793 ms
5  ae-3-0.cr0.dca20.tbone.rr.com (66.109.6.70)  38.932 ms  38.914 ms  38.891 ms
6  so-1-1-1.a0.alb75.tbone.rr.com (66.109.1.49)  38.751 ms 107.14.19.135 (107.14.19.135)  32.755 ms ae-2-0.c1.nyc90.tbone.rr.com (66.109.1.49)  33.969 ms
7  xe-0-1-1.er2.iad10.us.above.net (64.125.12.61)  33.925 ms  27.845 ms  31.455 ms
8  xe-5-1-0.cr2.dca2.us.above.net (64.125.29.77)  41.067 ms xe-4-1-0.cr2.dca2.us.above.net (64.125.29.214)  35.830 ms xe-5-1-0.cr2.dca2.us.above.net (64.125.29.77)  34.030 ms
9  xe-3-2-0.cr2.lga5.us.above.net (64.125.26.110)  43.372 ms xe-2-2-0.cr2.lga5.us.above.net (64.125.26.106)  40.800 ms  40.754 ms
10  xe-0-0-1.mpr2.ewr2.us.above.net (64.125.31.173)  39.274 ms  39.242 ms  41.460 ms
11  208.184.34.234.IPYX-069067-ZYO.above.net (208.184.34.234)  86.552 ms  86.509 ms  75.991 ms
12  openvz1.trouble-free.net (69.10.46.218)  37.707 ms  33.969 ms  34.756 ms
13  ginka.armageddon.org (209.159.155.76)  36.353 ms  33.246 ms  36.877 ms
****@****-AO722:~$ armageddon.org


and ping

Code Select
***@****-AO722:~$ ping armageddon.org
PING armageddon.org (209.159.155.76) 56(84) bytes of data.
64 bytes from ginka.armageddon.org (209.159.155.76): icmp_req=1 ttl=52 time=34.9 ms
64 bytes from ginka.armageddon.org (209.159.155.76): icmp_req=2 ttl=52 time=40.2 ms
64 bytes from ginka.armageddon.org (209.159.155.76): icmp_req=3 ttl=52 time=82.2 ms
64 bytes from ginka.armageddon.org (209.159.155.76): icmp_req=4 ttl=52 time=34.6 ms
64 bytes from ginka.armageddon.org (209.159.155.76): icmp_req=5 ttl=52 time=37.7 ms
64 bytes from ginka.armageddon.org (209.159.155.76): icmp_req=6 ttl=52 time=34.0 ms
64 bytes from ginka.armageddon.org (209.159.155.76): icmp_req=7 ttl=52 time=39.7 ms
64 bytes from ginka.armageddon.org (209.159.155.76): icmp_req=8 ttl=52 time=46.2 ms
64 bytes from ginka.armageddon.org (209.159.155.76): icmp_req=9 ttl=52 time=52.8 ms
64 bytes from ginka.armageddon.org (209.159.155.76): icmp_req=10 ttl=52 time=62.0 ms
64 bytes from ginka.armageddon.org (209.159.155.76): icmp_req=11 ttl=52 time=74.1 ms
64 bytes from ginka.armageddon.org (209.159.155.76): icmp_req=12 ttl=52 time=85.6 ms
64 bytes from ginka.armageddon.org (209.159.155.76): icmp_req=13 ttl=52 time=94.4 ms
64 bytes from ginka.armageddon.org (209.159.155.76): icmp_req=14 ttl=52 time=36.2 ms
64 bytes from ginka.armageddon.org (209.159.155.76): icmp_req=15 ttl=52 time=33.9 ms
64 bytes from ginka.armageddon.org (209.159.155.76): icmp_req=16 ttl=52 time=34.6 ms
64 bytes from ginka.armageddon.org (209.159.155.76): icmp_req=17 ttl=52 time=32.8 ms
64 bytes from ginka.armageddon.org (209.159.155.76): icmp_req=18 ttl=52 time=32.8 ms
64 bytes from ginka.armageddon.org (209.159.155.76): icmp_req=19 ttl=52 time=33.2 ms
64 bytes from ginka.armageddon.org (209.159.155.76): icmp_req=20 ttl=52 time=33.3 ms
64 bytes from ginka.armageddon.org (209.159.155.76): icmp_req=21 ttl=52 time=33.4 ms
64 bytes from ginka.armageddon.org (209.159.155.76): icmp_req=22 ttl=52 time=34.9 ms
64 bytes from ginka.armageddon.org (209.159.155.76): icmp_req=23 ttl=52 time=34.6 ms
64 bytes from ginka.armageddon.org (209.159.155.76): icmp_req=24 ttl=52 time=32.5 ms
Fredd-
i love being a nobles health points
May 03, 2013, 02:49:55 AM #427
Once again for lag, the best way to assist staff is to do a trace route and a ping. Thus the thread! Knowledge is power. Whoosh!
May 03, 2013, 03:08:11 AM #428
Quote from: Jeshin on May 03, 2013, 02:49:55 AM
Once again for lag, the best way to assist staff is to do a trace route and a ping. Thus the thread! Knowledge is power. Whoosh!

This is misleading, because not all lag is due to latency. Recent lag seems to have more to do with the server itself, like a memory leak in the code or something. Which is why it cleared up after Morgenes' reboot but slowly came back.
Quote from: IAmJacksOpinion on May 20, 2013, 11:16:52 PM
Masks are the Armageddon equivalent of Ed Hardy shirts.
May 03, 2013, 03:25:25 AM #429
Yes. The trace route and ping allows them to rule out network issues and focus on server issues or vice versa.
May 03, 2013, 04:32:35 PM #430
Here's mine:

Code Select
Reply from 209.159.155.76: bytes=32 time=19ms TTL=57
Reply from 209.159.155.76: bytes=32 time=18ms TTL=57
Reply from 209.159.155.76: bytes=32 time=19ms TTL=57
Reply from 209.159.155.76: bytes=32 time=18ms TTL=57
Reply from 209.159.155.76: bytes=32 time=17ms TTL=57
Reply from 209.159.155.76: bytes=32 time=19ms TTL=57
Reply from 209.159.155.76: bytes=32 time=19ms TTL=57
Reply from 209.159.155.76: bytes=32 time=18ms TTL=57
Reply from 209.159.155.76: bytes=32 time=19ms TTL=57
Reply from 209.159.155.76: bytes=32 time=18ms TTL=57
Reply from 209.159.155.76: bytes=32 time=19ms TTL=57
Reply from 209.159.155.76: bytes=32 time=21ms TTL=57
Reply from 209.159.155.76: bytes=32 time=18ms TTL=57
Reply from 209.159.155.76: bytes=32 time=18ms TTL=57
Reply from 209.159.155.76: bytes=32 time=19ms TTL=57
Reply from 209.159.155.76: bytes=32 time=19ms TTL=57
Reply from 209.159.155.76: bytes=32 time=17ms TTL=57
Reply from 209.159.155.76: bytes=32 time=17ms TTL=57
Reply from 209.159.155.76: bytes=32 time=17ms TTL=57
Reply from 209.159.155.76: bytes=32 time=19ms TTL=57
Reply from 209.159.155.76: bytes=32 time=18ms TTL=57
Reply from 209.159.155.76: bytes=32 time=17ms TTL=57
Reply from 209.159.155.76: bytes=32 time=18ms TTL=57
Reply from 209.159.155.76: bytes=32 time=17ms TTL=57
Reply from 209.159.155.76: bytes=32 time=17ms TTL=57
Reply from 209.159.155.76: bytes=32 time=18ms TTL=57
Reply from 209.159.155.76: bytes=32 time=19ms TTL=57
Reply from 209.159.155.76: bytes=32 time=19ms TTL=57
Reply from 209.159.155.76: bytes=32 time=19ms TTL=57
Reply from 209.159.155.76: bytes=32 time=18ms TTL=57
Reply from 209.159.155.76: bytes=32 time=18ms TTL=57
Reply from 209.159.155.76: bytes=32 time=22ms TTL=57
Reply from 209.159.155.76: bytes=32 time=21ms TTL=57
Reply from 209.159.155.76: bytes=32 time=17ms TTL=57
Reply from 209.159.155.76: bytes=32 time=18ms TTL=57
Reply from 209.159.155.76: bytes=32 time=19ms TTL=57
Reply from 209.159.155.76: bytes=32 time=18ms TTL=57
Reply from 209.159.155.76: bytes=32 time=20ms TTL=57
Reply from 209.159.155.76: bytes=32 time=18ms TTL=57
Reply from 209.159.155.76: bytes=32 time=17ms TTL=57
Reply from 209.159.155.76: bytes=32 time=18ms TTL=57
Reply from 209.159.155.76: bytes=32 time=18ms TTL=57
Reply from 209.159.155.76: bytes=32 time=18ms TTL=57
Reply from 209.159.155.76: bytes=32 time=18ms TTL=57
Reply from 209.159.155.76: bytes=32 time=18ms TTL=57
Reply from 209.159.155.76: bytes=32 time=17ms TTL=57

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

  1    <1 ms    <1 ms    <1 ms  ELEMENTS [***.***.*.*]
  2     *        *        *     Request timed out.
  3    11 ms    10 ms    11 ms  ***.***.***.*
  4    21 ms    22 ms    19 ms  216.113.122.98
  5    18 ms    19 ms    19 ms  eqix-ny2.interserver.com [198.32.118.45]
  6    19 ms    19 ms    18 ms  openvz1.trouble-free.net [69.10.46.218]
  7    18 ms    18 ms    17 ms  ginka.armageddon.org [209.159.155.76]

Trace complete.
Child, child, if you come to this doomed house, what is to save you?

A voice whispers, "Read the tales upon the walls."
May 03, 2013, 09:03:20 PM #431
Really really bad, right now.
I remember recruiting this Half elf girl. And IMMEDIATELY taking her out on a contract. Right as we go into this gith hole I tell her "Remember your training, and you'll be fine." and she goes "I have no training." Then she died
May 03, 2013, 11:59:39 PM #432
Can't even log in properly at this point.
Sometimes, severity is the price we pay for greatness
May 04, 2013, 12:12:37 AM #433
Hm, this is quite bad.  Ping times still in the 18-20ms range.  Definitely not network related.  And with ~50 players online, it doesn't seem to have anything to do with current player populations.
Child, child, if you come to this doomed house, what is to save you?

A voice whispers, "Read the tales upon the walls."
May 04, 2013, 12:29:33 AM #434
My traces and pings seem to be coming back fairly clean, yet I am still experiencing bursts of frequent lag for hours on end.

I think this is actually the Ginka server stalling and not a connection issue.

I don't know, I'm not a network/pc guru to that extent.
Quote from: James de Monet on April 09, 2015, 01:54:57 AM
My phone now autocorrects "damn" to Dman.
Quote from: deathkamon on November 14, 2015, 12:29:56 AM
The young daughter has been filled.
May 04, 2013, 01:58:33 AM #435
Yeah my ping is coming back ~90-100ms but I am also experiencing significant lag in game.
May 04, 2013, 06:37:57 AM #436
.... been saying this for a few days, now.
Quote from: IAmJacksOpinion on May 20, 2013, 11:16:52 PM
Masks are the Armageddon equivalent of Ed Hardy shirts.
May 04, 2013, 07:40:25 AM #437
Here's mine. This is all moonspeak to me but it doesn't look good.

Code Select
Traceroute has started ...

traceroute to 209.159.155.76 (209.159.155.76), 64 hops max, 40 byte packets
1  192.168.4.1 (192.168.4.1)  18.606 ms  1.597 ms  1.476 ms
2  * * *
3  ip-86-49-52-1.net.upcbroadband.cz (86.49.52.1)  11.046 ms  27.336 ms  10.676 ms
4  84.116.221.225 (84.116.221.225)  109.462 ms  110.406 ms  110.551 ms
5  84.116.135.1 (84.116.135.1)  137.951 ms  135.289 ms  113.363 ms
6  uk-lon02a-rd2-xe-0-2-2.aorta.net (84.116.133.93)  130.538 ms  176.606 ms 84.116.133.214 (84.116.133.214)  106.913 ms
7  us-nyc01c-rd1-pos-3-0-0.aorta.net (213.46.160.126)  116.662 ms us-nyc01c-rd1-pos-1-0-0.aorta.net (213.46.160.206)  112.720 ms us-nyc01c-rd1-pos-3-0-0.aorta.net (213.46.160.126)  113.679 ms
8  84.116.135.98 (84.116.135.98)  111.552 ms  132.028 ms  112.204 ms
9  above.net (198.32.118.25)  112.222 ms  120.108 ms  142.055 ms
10  xe-4-1-0.cr2.lga5.us.above.net (64.125.30.209)  113.103 ms  117.103 ms  113.870 ms
11  xe-0-0-1.mpr2.ewr2.us.above.net (64.125.31.173)  108.962 ms  108.379 ms  105.221 ms
12  208.184.34.234.IPYX-069067-ZYO.above.net (208.184.34.234)  120.685 ms  119.995 ms  122.125 ms
13  openvz1.trouble-free.net (69.10.46.218)  119.565 ms  115.395 ms  115.204 ms
14  ginka.armageddon.org (209.159.155.76)  114.689 ms  120.688 ms  117.383 ms
Czar of City Elves.
May 04, 2013, 09:11:30 AM #438
Still bad. Yep.
I remember recruiting this Half elf girl. And IMMEDIATELY taking her out on a contract. Right as we go into this gith hole I tell her "Remember your training, and you'll be fine." and she goes "I have no training." Then she died
May 04, 2013, 10:08:20 AM #439
Ok, the game is pretty much unplayable for me right now.
I remember recruiting this Half elf girl. And IMMEDIATELY taking her out on a contract. Right as we go into this gith hole I tell her "Remember your training, and you'll be fine." and she goes "I have no training." Then she died
May 04, 2013, 10:13:27 AM #440
I'm experiencing pretty solid lag but I'm not seeing the cause....

Code Select

C:\>tracert armageddon.org

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

  1     1 ms     1 ms     1 ms  192.168.1.1
  2    37 ms    19 ms    30 ms  cpe-76-176-32-1.san.res.rr.com [76.176.32.1]
  3    10 ms     9 ms     8 ms  tge1-1.crlscaij-cer02.socal.rr.com [76.166.18.10
1]
  4    18 ms    14 ms    15 ms  tge0-8-0-1.sndhcaax-ccr02.socal.rr.com [72.129.1
.118]
  5    20 ms    16 ms    15 ms  agg22.tustcaft-ccr01.socal.rr.com [72.129.1.2]
  6    17 ms    23 ms    15 ms  ae-6-0.cr0.lax30.tbone.rr.com [66.109.6.214]
  7    13 ms    16 ms    14 ms  ae-1-0.pr0.lax10.tbone.rr.com [66.109.6.131]
  8    14 ms    16 ms    13 ms  xe-1-3-0.mpr1.lax12.us.above.net [64.125.13.45]

  9    19 ms    17 ms    21 ms  xe-3-0-0.cr2.lax112.us.above.net [64.125.30.29]

10    53 ms    52 ms    51 ms  xe-3-2-0.cr2.iah1.us.above.net [64.125.30.49]
11    78 ms    78 ms    79 ms  xe-5-0-0.cr2.dca2.us.above.net [64.125.31.250]
12    82 ms    83 ms    87 ms  xe-3-2-0.cr2.lga5.us.above.net [64.125.26.110]
13   126 ms    84 ms    82 ms  xe-0-0-1.mpr2.ewr2.us.above.net [64.125.31.173]

14    82 ms    82 ms    82 ms  208.184.34.234.IPYX-069067-ZYO.above.net [208.18
4.34.234]
15    82 ms    82 ms    83 ms  openvz1.trouble-free.net [69.10.46.218]
16    83 ms    82 ms    83 ms  ginka.armageddon.org [209.159.155.76]

Trace complete.
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.
May 04, 2013, 11:04:28 AM #441 Last Edit: May 04, 2013, 02:05:11 PM by evil_erdlu
I doubt we need any more trace route or ping logs.. I'm currently using some shitty internet connection from my local GSM provider and my ping 320 ms. But in game, I realized two things;

1. As visible, it's way too laggy.
2. Commands with no 'before' delay are getting a 'before' delay. For example; if I wait enough to ensure my character has no delay in progress, then type 'n;l n' it sometimes looks north - response coming nearly instantly - , then moves north in a second or two.

Damn.. I'm in the field in the middle of nowhere and I'm forced to stay here. There's nothing else to do here. I would be delighted if this could be fixed.

Edit: Not 32 ms ping of course.. It's 320 ms.. Sorry about the confusion, I seem to have forgotten the zero.
Q  : Where do you piss?
Yam: On elves.
Q  : And if the area, lacks elves at the given time?
Yam: Scan.
May 04, 2013, 12:13:01 PM #442
The last 2-3 weeks I have seen a performance hit. Did we switch providers? Can I help in anyway to resolve the game performance issues? I am willing to contribute knowledge, finical help, etc to help work on getting the user experience resolved.

Just let me know if you need anything.

Corey
Print
Go Up Pages 1 ... 16 17 18
User actions