Zugg Software :: View topic - [3.31] Why does CMUD turn into a CPU hog when speedwalking?

Posted: Thu Nov 04, 2010 8:35 am

Something I just noticed and am curious about. Why does speedwalking such as .5n spike my CPU usage roughly 50%. I couldn't test in the untitled session, so I had to create a new session to some random mud. Once you do that set your delay between commands to 5 or 10 seconds and enter a speedwalk on the command line without being connected to the mud .5n for example. For me on this vista machine CMUD jumps from 0 to 44-51 percent usage with no other triggers in the new session or even connected to the MUD.

Posted: Thu Nov 04, 2010 8:08 pm

Doesn't do this for me here. Have no idea since I'd normally blame this on scripts or something. It doesn't even sound like you are using the mapper. Might try rebooting your computer or something simple like that. But in a new session for me here doing .5n doesn't take any CPU time at all.

Posted: Thu Nov 04, 2010 9:05 pm

No scripts running and mapper is not in use. This is a fresh clean package on some random mud which I'm not even connected to just using in offline mode (this happens when connected too of course). I had rebooted when I tested before making the post, and I just rebooted again to double check and it still does the same thing. You can see in the screen shot where CPU usage jumps from next to nothing to 50% give or take a couple from when the speed walk is first entered.

Posted: Fri Nov 05, 2010 5:00 pm

All I can suggest is deleting your CMUD files and reinstalling. You have changed your session defaults somewhere because your session window is showing the timestamp column on the left, which is not enabled by default. That doesn't cause any CPU spike itself, but it tells me that you are not running a clean installation, which makes it hard to compare here.

I just tried the above test on 3 different computers with clean installs using one of the preinstalled session icons, and none of them showed any CPU spike like this, including our Vista system. So I don't really know what else to suggest. But it's possible one of the preinstalled packages, like English Directions or English Keypad have gotten corrupted or something. But it's definitely specific to just your computer.

Posted: Fri Nov 05, 2010 6:58 pm

Yeah I went to session > scrollback in the preferences window and clicked show timestamps, to show that the issue was happening while there was a delay between commands set. I'll try a fresh install and see if that fixes it... post back in a few.

Posted: Fri Nov 05, 2010 7:51 pm

I had zmapper installed for evaluation so I trashed that on the chance that was a problem. Did a complete uninstall of CMUD and all settings related to it then reinstalled. Rebooted the PC, and opened one of the preinstalled sessions offline, went to the scripting tab in the Preferences menu and set the delay to 4000. I then typed .5e on the command line and took the screen shot after 4 of the 5 commands had been sent. The problem is still there any other suggestions?

Posted: Fri Nov 05, 2010 10:22 pm

Posted: Sat Nov 06, 2010 4:35 am

I was able to recreate this. The key is the 4 second delay between commands. It's normally 5 milliseconds. When you stick with the default there is no spike. I suspect the spike comes from the monitoring for precise passage of 4 seconds.

Posted: Sat Nov 06, 2010 9:32 am

Thanks for reading the first post and trying to reproduce Tech. I think the bug could possibly be in the delay too. When you do a fresh install of CMUD, then load any session for the first time, in Preferences>scripting>general scripting the delay between sending lines is set to 0. Entering just a few directions through a speedwalk has no impact on CPU usage with this setting. You need to set the delay between sending lines to something larger than 0. The delay doesn't have to be as large as 4000ms though, I can get the 50 percent CPU spike from CMUD with a delay of 500ms. If you put together a map and have a delay set, then speedwalk by clicking on a room on the map you should see the spike as well. As long as there is a delay set. This is actually an old bug that I am surprised no one has ever found. I saw the exact same thing happening in zMUD 7.21 earlier when testing out of curiosity.

Posted: Mon Nov 08, 2010 5:53 pm

Bah, sorry I missed this part:

Posted: Mon Nov 08, 2010 11:17 pm

Interesting. When I looked into this a bit more, I found a way to prevent it from using 100% CPU during the Send Delay. But in the process, I also found a pretty serious bug that if you try to exit CMUD while in the middle of a speedwalk with the SendDelay enabled, CMUD will hang.

Both should be fixed in the next update.