Laggy Penn?
This has been driving me nuts, hopefully someone knows what the deal is. I've noticed on some PennMUSH games, there's a slight delay between seeing an object's name and its description when looked at. There's just a slight pause, enough to make the title seem separate from the description. I've also noticed that this doesn't happen on M*U*S*H.
I've spent a long time spelunking through mush.cnf and the help files and couldn't find anything hinting as to how to handle this. The boxes I'm testing this game on are both very fast, and one is local (which rules out net lag). Is there a compile option or config directive that sucks resources to the point where this delay becomes that pronounced? I've never seen this problem on MUX, even the old versions.
Any advice is appreciated!
- Kelvin McCorvin's blog
- Login or register to post comments
Click 
Total longshot
Total longshot, but does it depend on the client you use? Different for tf, say, vs mushclient? If so, I'd go further and ask if it depended on whether you were using the pueblo protocol or not.
I don't think so, I'm using
I don't think so, I'm using the latest MUSHclient and tested against a very vanilla Penn and M*U*S*H. I have disabled Pueblo, as it annoys me to no end :)
Is it possible you have
Is it possible you have something like a function- or cpu-intensive descformat? (I wouldn't think a lot of functions would make much difference, generally, but your client may be slow parsing a lot of ANSI, for example, and if you have calls to anything like sql(), lsearch(), etc, anywhere in there it's going to slow things down.)
I've seen this happen with
I've seen this happen with standard rooms as well, along with some hardcoded commands, so I think I've ruled this out (maybe).
I'm noticing that the parser is pretty sluggish too, I wonder if I've got a compile-time or config directive on that's slowing things down.