Lag?

by Unknown

Back to Common Grounds.

Unknown2005-01-27 10:19:31
Anyone else been lagging a lot on Lusternia lately? I've been getting lag spurts of 15 seconds, dropped, etc.
Flow2005-01-27 10:37:30
Yes! I've been getting that alot.
Ialie2005-01-27 16:05:47
Dropped like a sack of potatos.
Shiri2005-01-27 17:16:57
Always had lag since the start, getting BETTER now though. 0_o'
Lunarisiil2005-01-27 17:18:30
I was having awful lag... Not good when you're hunting.
Unknown2005-01-27 18:42:43
I've had bad lag many times... always blamed it on my dial-up connection.
Richter2005-01-27 19:45:21
I have dial up and never lag.

Except on that one log of me fighting Bob, and all of a sudden, it lags for 40 or so seconds. *twiddle* *scream* *spam* *death*
Unknown2005-01-27 21:36:04
Is it true that the further away you are from the Lusternian server, the larger the gap gets between you sending a command and it returning?
Buho2005-01-27 22:44:22
QUOTE(Zaltan @ Jan 28 2005, 06:36 AM)
Is it true that the further away you are from the Lusternian server, the larger the gap gets between you sending a command and it returning?
37627



In a way that is true. It's not physical distance thou, its how many "hops" or other computers you have to go through. Each time your computer goes through another server, that brings potential lag with it.

Not much you can really do about it, but if you want to look at how many hops it's pretty easy. If you rn windows open a command prompt (Start-Run CMD). Then type TRACERT LUSTERNIA.COM That will show you ever network you go through to get to us. Also shows the Milliseconds(MS) that it takes for it to get a reply from that server. A bunch of *'s means it took so long to get a reply it gave up, and that is probably where your biggest lag comes from.
Richter2005-01-27 23:11:22
The one at work gave up after 6. *eye*

Though, I can't play from here anyway.
Unknown2005-01-28 05:26:28
QUOTE(Buho @ Jan 27 2005, 06:44 PM)
In a way that is true.  It's not physical distance thou, its how many "hops" or other computers you have to go through.  Each time your computer goes through another server, that brings potential lag with it. 

Not much you can really do about it, but if you want to look at how many hops it's pretty easy.  If you rn windows open a command prompt (Start-Run CMD).  Then type TRACERT LUSTERNIA.COM  That will show you ever network you go through to get to us.  Also shows the Milliseconds(MS) that it takes for it to get a reply from that server.  A bunch of *'s means it took so long to get a reply it gave up, and that is probably where your biggest lag comes from.
37699



The speed of light is a limiting factor if you're talking about serious distances - such as over the Atlantic or Pacific ocean.
Unknown2005-01-28 08:34:01
Ouch, 30 hops for me, the last 20 of which timed out before the window closed itself doh.gif

Is there really no way to improve that? I'm pretty sure I remember a guy on achaea years ago by the name of Derk who used to brag about how he arranged himself 1 server away from achaea and could change guard on some people in the middle of their combo and throw them tongue.gif
Amphitrite2005-01-28 09:10:13
Well im in england and ive never had any lag problems. Im playing from a fast university connection though..
Shiri2005-01-28 11:36:24
576k from England. Shouldn't be THAT bad, though. Here lags more'n Achaea, funnily enough.
celahir2005-01-28 12:55:44
A friend of mine everytime he enters the sewers he gets d/c and has to restart the computer when it happens...
Flow2005-01-28 14:01:52
CODE
Tracing route to lusternia.com
over a maximum of 30 hops:

 1     *        *        *     Request timed out.
 2     *        *        *     Request timed out.
 3     *        *        *     Request timed out.
 4     *        *        *     Request timed out.
 5     *        *        *     Request timed out.
 6     *        *        *     Request timed out.
 7     *        *        *     Request timed out.
 8     *        *        *     Request timed out.
 9     *        *        *     Request timed out.
10     *        *        *     Request timed out.
11     *        *        *     Request timed out.
12     *        *        *     Request timed out.
13     *        *        *     Request timed out.
14     *        *        *     Request timed out.
15     *        *        *     Request timed out.
16     *        *        *     Request timed out.
17     *        *        *     Request timed out.
18     *        *        *     Request timed out.
19     *        *        *     Request timed out.
20     *        *        *     Request timed out.
21     *        *        *     Request timed out.
22     *        *        *     Request timed out.
23     *        *        *     Request timed out.
24     *        *        *     Request timed out.
25     *        *        *     Request timed out.
26     *        *        *     Request timed out.
27     *        *        *     Request timed out.
28     *        *        *     Request timed out.
29     *        *        *     Request timed out.
30     *        *        *     Request timed out.

Trace complete.

sad.gif
Gwylifar2005-01-28 22:32:59
Traceroute reports are of less value every year since more and more routers ignore the packets since more and more malevolent little twerps use them for DoS (denial of service) attacks.

The way a traceroute actually works is quite fascinating, as it's really very non-deterministic. Various packets are sent out for each step and since they can take different routes, traceroutes can give you displays that make no sense whatsoever. But they're still useful when they're not blocked.
Unknown2005-01-30 09:14:53
QUOTE
Tracing route to lusternia.com
over a maximum of 30 hops:

  1  156 ms  156 ms  141 ms  254.reserved.callplus.net.nz
  2  172 ms  531 ms  266 ms  173.reserved.callplus.net.nz
  3  156 ms  172 ms  172 ms  pvc800.mr2.akl.tranzpeer.net
  4  172 ms  172 ms  156 ms  f0-0.5.cpiak1-r1.tranzpeer.net
  5  172 ms  171 ms  141 ms  61.14.140.81
  6  188 ms  187 ms  188 ms  po2-2.gw2.syd1.asianetcom.net
  7  281 ms  312 ms  391 ms  po6-2.cr1.nrt1.asianetcom.net
  8    *        *      297 ms  gi5-0.gw1.nrt2.asianetcom.net
  9  328 ms  313 ms  296 ms  as6461.nspixp2.wide.ad.jp
10    *      313 ms  312 ms  so-2-1-0.cr2.nrt3.jp.above.net
11  438 ms  391 ms  421 ms  so-3-2-1.cr1.sjc3.us.above.net
12  375 ms  422 ms  406 ms  so-6-3-0.mpr3.sjc2.us.above.net
13  438 ms  406 ms  390 ms  so-2-0-0.er10a.sjc2.us.above.net
14    *        *        *    Request timed out.
15    *        *        *    Request timed out.
16    *        *        *    Request timed out.
17    *        *        *    Request timed out.
18    *        *        *    Request timed out.
19    *        *        *    Request timed out.
20    *        *        *    Request timed out.
21    *        *        *    Request timed out.
22    *        *        *    Request timed out.
23    *        *        *    Request timed out.
24    *        *        *    Request timed out.
25    *        *        *    Request timed out.
26    *        *        *    Request timed out.
27    *        *        *    Request timed out.
28    *        *        *    Request timed out.
29    *        *        *    Request timed out.
30    *        *        *    Request timed out.

Trace complete.

Doesn't look too good, whatever it means. Oh well, it looks better than Flow's. wink.gif

I play on a 56kbps (but usually 52kbps), from New Zealand, but I don't get too much lag.

I made up this little ping-testing zMUD script:

CODE
#CLASS {Ping}
#ALIAS ping {
 #VARIABLE Ping %secs
 #CR
 #TEMP {^%dh, %dm} {#VARIABLE Ping {%eval( %secs - @Ping)}} "" {prompt|nocr}
 #ALARM +0.5 {#ECHO Pong took @{Ping}ms.}
 }
#VARIABLE Ping {437}
#CLASS 0

It's not perfect, but just an estimate. Just type "ping" and it tells you how many ms it took.

I averaged around 440ms. tongue.gif
Rauros2005-01-31 04:43:56
Not more lag than I always get. I never hunt anymore for fear of lag death.
Unknown2005-01-31 10:19:45
I can't even ping the server! :cry: