Mudlet extremely slow

[tirah93]

Around a certain time of the day, from midday to the evening with some deviations, my mudlet get really slow while playing Lusternia.
This is not only like this at my place, but at a friends too and only happens with mudlet, not with nexus for example.
My N value goes from 2 to 56 at those time, typically around 16.

This is my tracert, maybe it helps


1 2 ms 4 ms 2 ms XXXXXXXX
2 11 ms 22 ms 15 ms XXXXXXXX
3 11 ms 11 ms 12 ms XXXXXXXXX
4 15 ms 14 ms 14 ms bbrt.ol-0-1-xe-1-1-0.ewe-ip-backbone.de [212.6.1
14.249]
5 15 ms 16 ms 15 ms bbrt.hb-2-xe-0-3-0.ewe-ip-backbone.de [80.228.90
.97]
6 35 ms 39 ms 34 ms bbrt.lon-0-10ge-7-0-0.ewe-ip-backbone.de [212.6.
114.22]
7 * * * Zeitüberschreitung der Anforderung. <---Means it got a timeout
8 151 ms 150 ms 155 ms xe-5-3-0-70.er1.Chi2.Servernap.net [66.252.3.133
]
9 138 ms 137 ms 139 ms te-9-4.csr2.Chi3.Servernap.net [66.252.0.69]
10 141 ms 144 ms 139 ms po-102.ddr1.Chi3.Servernap.net [66.252.0.130]
11 136 ms 136 ms 138 ms http://www.lusternia.com [69.65.42.86]

[phasma]

Hard to say what could be causing this, but I can certainly say with a high level of confidence that Mudlet is not the issue here.

Latency to lusternia.com has been pretty poor lately. I'd just mark this down to the internet being the internet, to be honest.

[tirah93]

really? But it only happens with mudlet

[Silvine]

On a different game I know someone else had this or a similar issue, To fix it he disabled the mapping demo that was or possibly still is part of the install. So I'd take a look for something that didn't below there and untick it.

[tirah93]

It seems I do not even have an option for that

[phasma]

There is no 'mapping demo' that comes with the default install. There is a basic mapping script, but this would definitely not cause the issues claimed here. Again, this is almost certainly not a Mudlet issue. Have you tried anything else to debug this aside of connecting from elsewhere?

[tirah93]

not really, I don't really know what could help

[Silvine]

Its the mapping script to which I refer and it did cause issues for the person I mentioned. He turned it off and the problem went away. I don't know how or why or what caused it, but turning it off solved his problem.

[Vadi]

If the mapping script was causing the slowdown, the S number would be the high one, not N.

Maybe some firewall settings on your computer were affecting Mudlets network performance? Otherwise, this has never been an issue with Mudlet and generally Mudlet does not affect its own network speed - so it's highly unlikely that this is the case.

[Vadi]

Could you get a trace while this slowdown is happening?