Thread Rating:
  • 0 Vote(s) - 0 Average
  • 1
  • 2
  • 3
  • 4
  • 5

Why does IN lag when it shouldn't?
#1

Hi. Why does Imagine Nation lag when it shouldn't?

I tried logging on to another UO server just to compare the ping and the lag.

To INs server I have 115ms ping. (no timeouts)

To the other server I have 160ms ping (no timeouts).

At IN I lag a lot, its different between times, but its mostly there and it's feeling like if I would have 1000ms. It makes me spike every 1-2 tiles and the spells are 1 second delayed.

At the other server I noticed no lag at all, it's all very fluent, and I have 50ms less good ping to that server!

The only difference between the two servers is that IN is running on RunUO and that one is running on Sphere. That makes me think that maybe it is some script that is causing the lag, some script that is always looping in the background or something.

It feels like the lag is getting worse when in duels, so I don't know if there's some script that involves combat that is causing it, but it could be.

Could you please take a look at this? Because with my current ping and no timeouts I shouldn't be lagging, especially not the way I (and many others) are.

It could very well cause a lot of players to quit if we don't figure out what is causing the lag, so please take your time and look through the scripts, it's well worth your time if you find something that could cause it.

Edit: I guess it could also be the server computer not being able to run a RunUO server, but that would have to mean that it's a very shitty computer, or a computer with very shitty RAM, and I doubt that's the case.
#2

My ping to IN:

Reply from 109.169.73.50: bytes=32 time=119ms TTL=114
Reply from 109.169.73.50: bytes=32 time=134ms TTL=114
Reply from 109.169.73.50: bytes=32 time=115ms TTL=114
Reply from 109.169.73.50: bytes=32 time=143ms TTL=114
Reply from 109.169.73.50: bytes=32 time=121ms TTL=114
Reply from 109.169.73.50: bytes=32 time=114ms TTL=114
Reply from 109.169.73.50: bytes=32 time=136ms TTL=114
Reply from 109.169.73.50: bytes=32 time=117ms TTL=114
Reply from 109.169.73.50: bytes=32 time=121ms TTL=114
Reply from 109.169.73.50: bytes=32 time=114ms TTL=114
Reply from 109.169.73.50: bytes=32 time=113ms TTL=114
Reply from 109.169.73.50: bytes=32 time=129ms TTL=114
Reply from 109.169.73.50: bytes=32 time=126ms TTL=114
Reply from 109.169.73.50: bytes=32 time=122ms TTL=114
Reply from 109.169.73.50: bytes=32 time=113ms TTL=114
Reply from 109.169.73.50: bytes=32 time=113ms TTL=114
Reply from 109.169.73.50: bytes=32 time=115ms TTL=114
Reply from 109.169.73.50: bytes=32 time=113ms TTL=114
Reply from 109.169.73.50: bytes=32 time=124ms TTL=114
Reply from 109.169.73.50: bytes=32 time=123ms TTL=114
Reply from 109.169.73.50: bytes=32 time=124ms TTL=114
Reply from 109.169.73.50: bytes=32 time=114ms TTL=114
Reply from 109.169.73.50: bytes=32 time=114ms TTL=114
Reply from 109.169.73.50: bytes=32 time=113ms TTL=114
Reply from 109.169.73.50: bytes=32 time=113ms TTL=114
Reply from 109.169.73.50: bytes=32 time=117ms TTL=114
Reply from 109.169.73.50: bytes=32 time=113ms TTL=114

My ping to the other server:

Reply from **********: bytes=32 time=175ms TTL=40
Reply from **********: bytes=32 time=161ms TTL=40
Reply from **********: bytes=32 time=162ms TTL=40
Reply from **********: bytes=32 time=163ms TTL=40
Reply from **********: bytes=32 time=163ms TTL=40
Reply from **********: bytes=32 time=160ms TTL=40
Reply from **********: bytes=32 time=163ms TTL=40
Reply from **********: bytes=32 time=163ms TTL=40
Reply from **********: bytes=32 time=160ms TTL=40
#3

Western MA. Verizon DSL.

Pinging game.in-uo.net [109.169.73.50] with 32 bytes of data:
Reply from 109.169.73.50: bytes=32 time=49ms TTL=117
Reply from 109.169.73.50: bytes=32 time=45ms TTL=117
Reply from 109.169.73.50: bytes=32 time=73ms TTL=117
Reply from 109.169.73.50: bytes=32 time=117ms TTL=117

Ping statistics for 109.169.73.50:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 45ms, Maximum = 117ms, Average = 71ms



Pinging game.in-uo.net [109.169.73.50] with 32 bytes of data:
Reply from 109.169.73.50: bytes=32 time=46ms TTL=117
Reply from 109.169.73.50: bytes=32 time=50ms TTL=117
Reply from 109.169.73.50: bytes=32 time=50ms TTL=117
Reply from 109.169.73.50: bytes=32 time=48ms TTL=117

Ping statistics for 109.169.73.50:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 46ms, Maximum = 50ms, Average = 48ms



Pinging game.in-uo.net [109.169.73.50] with 32 bytes of data:
Reply from 109.169.73.50: bytes=32 time=46ms TTL=117
Reply from 109.169.73.50: bytes=32 time=47ms TTL=117
Reply from 109.169.73.50: bytes=32 time=45ms TTL=117
Reply from 109.169.73.50: bytes=32 time=44ms TTL=117

Ping statistics for 109.169.73.50:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 44ms, Maximum = 47ms, Average = 45ms
#4

Well one way to test it is to login to my test server and see if you lag just as badly there.
I'll come find you ingame later today.
#5

Ответ от 109.169.73.50: число байт=32 время=232мс TTL=114
Ответ от 109.169.73.50: число байт=32 время=234мс TTL=114

Статистика Ping для 109.169.73.50:
Пакетов: отправлено = 99, получено = 99, потеряно = 0 (0% потерьWink,
Приблизительное время приема-передачи в мс:
min= 229мсек, max = 239 мсек, Среднее = 233 мсек


Трассировка маршрута к game.in-uo.net [109.169.73.50]
с максимальным числом прыжков 30:

1 1 ms <1 мс 1 ms 192.168.1.1
2 24 ms 29 ms 27 ms 195.5.5.202
3 35 ms 33 ms 34 ms 10.50.19.82
4 162 ms 159 ms 199 ms war-b1-link.telia.net [213.248.93.161]
5 161 ms 161 ms 163 ms hbg-bb2-link.telia.net [80.91.245.44]
6 294 ms 238 ms 238 ms nyk-bb2-link.telia.net [80.91.247.123]
7 237 ms 233 ms 233 ms nyk-b2-link.telia.net [80.91.245.247]
8 235 ms 234 ms 234 ms fortress-120799-nyk-b2.c.telia.net [213.248.83.1
06]
9 232 ms 232 ms 234 ms 208.116.63.207
10 237 ms 236 ms 237 ms 208.116.63.171
11 232 ms 233 ms 232 ms 109.169.73.50

Трассировка завершена.

[SIGPIC][/SIGPIC]
#6

Taran Wrote:Well one way to test it is to login to my test server and see if you lag just as badly there.
I'll come find you ingame later today.

I came back after a night of macroing and the lag is gone now. I still have the same ping, but no freezes AT ALL now, no packetloss today either.

I tried to duel some guy just to see if it would trigger the lag, but it was no change at all. I let him both hit me and cast spells on me, but nothing happened, so I don't think combat triggers it but somehow something must trigger it because I have the same ping and now it's completely gone.

The whole server seem to feel it too at the same time I do it, so I think it's a thing that is happening to everybody at the same time. Perhaps somebody macroing and somehow triggers a flawed RunUO script that loops in the background and makes everybody lag? That could be it I guess.

I can try to log on to your test server still but it won't matter much at this point since I don't have lag now, but maybe I do when you get back :p

My ping now:
Reply from 109.169.73.50: bytes=32 time=112ms TTL=114
Reply from 109.169.73.50: bytes=32 time=113ms TTL=114
Reply from 109.169.73.50: bytes=32 time=113ms TTL=114
Reply from 109.169.73.50: bytes=32 time=114ms TTL=114
Reply from 109.169.73.50: bytes=32 time=113ms TTL=114
Reply from 109.169.73.50: bytes=32 time=113ms TTL=114
Reply from 109.169.73.50: bytes=32 time=118ms TTL=114
Reply from 109.169.73.50: bytes=32 time=116ms TTL=114
Reply from 109.169.73.50: bytes=32 time=113ms TTL=114
Reply from 109.169.73.50: bytes=32 time=113ms TTL=114
Reply from 109.169.73.50: bytes=32 time=114ms TTL=114
Reply from 109.169.73.50: bytes=32 time=113ms TTL=114
Reply from 109.169.73.50: bytes=32 time=113ms TTL=114
Reply from 109.169.73.50: bytes=32 time=112ms TTL=114
Reply from 109.169.73.50: bytes=32 time=113ms TTL=114
Reply from 109.169.73.50: bytes=32 time=113ms TTL=114
Reply from 109.169.73.50: bytes=32 time=114ms TTL=114
Reply from 109.169.73.50: bytes=32 time=113ms TTL=114
Reply from 109.169.73.50: bytes=32 time=114ms TTL=114
Reply from 109.169.73.50: bytes=32 time=113ms TTL=114
Reply from 109.169.73.50: bytes=32 time=113ms TTL=114
Reply from 109.169.73.50: bytes=32 time=113ms TTL=114
Reply from 109.169.73.50: bytes=32 time=113ms TTL=114

(It's a little more stable but no big change)
#7

Type in the ShoutBox next time you get lag and I can check the server CPU/memory usage.
#8

Taran Wrote:Type in the ShoutBox next time you get lag and I can check the server CPU/memory usage.

Will do!
#9

We may have some noisy neighbors in our little VPS neighborhood.
#10

Taran Wrote:Type in the ShoutBox next time you get lag and I can check the server CPU/memory usage.

Taran, I had no lag at all today and then I joined an event (1vs1 autosupplied), as soon as I attacked my first opponent the lag came rushing back. Delays of 1-2 seconds and spikes all the time.

I told Shade how it happened and when, and he said that he found like 5000 event spawners that could be the reason for the lag, so lets hope that is it. But if you're on feel free to check the CPU usage and all that ;p If not then lets hope what Shade thinks is causing it is the reason Smile All of us at the tourney lagged a lot as soon as we started fighting tho, but not before that. After we had started fighting it never disapeared tho, I still have the lag and I've left the tourney arena a long time ago.

I also tried to fight with .BF turned on (didn't help). And I tried to fight with house caching down to 0 (didn't help). I think that whatever is starting to loop during the combat fights doesn't stop until you reboot the server. Lets hope it's the events, but if not good luck finding out what it is Wink

I hope that helps, at least a little bit, good luck now! Smile

- Ziggy
#11

We should host the next tourney in the old Green Acres are to see if that helps.
#12

But if it's a script that's looping then you should have gotten the lag when testing PvP out on my server as well.
I removed the spawners on there though so hopefully that's the issue.


Forum Jump:


Users browsing this thread: 1 Guest(s)