Zugg Software :: View topic - [3.16b] Anyone else seeing slowdowns from 24/7 gameplay?

Adept Joined: 10 Jan 2002 Posts: 264 Location: USA

Ok, been giving cmud a go again for about a week now...

got all the compatibility issues resolved, and fixed prolly 90% of the broke stuff that wasn't in report.

cmud does appear to be way faster then zmud with all my stuff loaded....

(Group) Ozzy: 'Triggers: 2257 Aliases: 272 Variables: 1129 Paths: 0 Macros: 50 Class Folders: 657 Mapped Zones: 275 with 30386 rooms. Menus: 4 Tabwords: 208 Status Windows: 5 Directions: 10 Buttons: 8'

but, i leave it running 24/7... and after a day or so, it starts to feel like zmud, just bogged down

i quit, reload and all is good again

at startup when i 1st run my session, peak memory is 106MB, then drops to 87MB... seems to be about the same within 10MB after 24hours
but no matter what it gets sluggish, i have tried disabling most of my classes a few at a time, does nothing... typing #IG speeds it back up

anyone else with a comparible # of settings and staying online 24/7 seeing this?

Posted: Fri Apr 16, 2010 7:15 am

I also notice the slowdown as regards the map movements.

The main problem is that the mapper moves extremely slow right from the beginning.

Say I have an alias to go to a specific area that contains 15 commands.
First, the mapper takes like 2-3 seconds to reach the destination and only then sends the whole list of commands to the mud.
And processor goes all the way up. (WinXP 64-bit, AMD 4000+)

After a few hours of play there comes the slowdown because that same alias takes like 5-6 seconds to complete (the Map moves slower).

I have disabled "Center map after every movement" but to no avail.

I would have liked to disable the Map when using aliases with more than 10 commands, but what's worse, when on Off Mode, the Map still follows the movements.

I recommended CMUD to a fellow mudder and he dismissed it on the account that the mapper is slow.

All I'm hoping is that all this issue is due to the Beta status, but I'm afraid it is not.

Adept Joined: 10 Jan 2002 Posts: 264 Location: USA

hrm, my slowdown completely clears if i #IG (disable triggers)

i use fastwalk in the mapper and our mud's built in "run" command, all the maper does is a #MOVE to the destination

Posted: Fri Apr 16, 2010 7:44 am

I also use fastwalk, that's why I said the mapper sends all the commands only after the mapper reaches the destination.

The mapper is so slow that I can track with my eyes as the mapper moves every room at the time.
I would very much like my mapper to move instantly to the destination!!!
How should I do that?

Wizard Joined: 22 Mar 2007 Posts: 2320

Private, if using #IG fixes it, it is almost certainly due to one or more of your triggers. I'm fairly sure that almost no one tries to run Cmud 24/7, but I believe Zugg has tested running it that long with no problems. Do you by chance use #WAIT or other commands that would create threads?

GURU Joined: 23 Dec 2000 Posts: 4834 Location: USA

I do. 3.14-3.16 were really the only versions that seemed to be really stable over the long-term (as opposed to being stable over a full session), and the versions after the commandline change really got some staying power.

The only reasons I shut down CMud now are because of bugs throwing AVs or otherwise raging out of control or Windows Updates.

Adept Joined: 10 Jan 2002 Posts: 264 Location: USA