Zugg Software :: View topic

Posted: Fri Sep 02, 2005 4:59 am

Been having some problems with zMUD lately, lag and crashes. Trying to figure out what's causing it, I noticed that #alarm, as well as showing alarms, shows pending triggers. I also noticed I had 225 pending triggers.

About 30 seconds later, I had 240 pending triggers. 10 secs after that, I got another access violation and had to reboot :P

I rebooted again, turned off my most resource-using script, and for about 10 mins, pending trigs stayed at 1/0. Then jumoed to 50. I turned off another script, and they started going down, then stayed at 20ish... my question is two-fold.

1) How many pending triggers is "safe" for zMUD to handle? At what point are you likely overloading it? (on a P4 3.2 with 1GB of ram, running nothing useage-intensive but zMUD, I.E., and virus scanner).

2) Is there a way to get a list of the actual pending triggers? Possibly try to figure out what's causing the backlog?

SubAdmin Joined: 18 Nov 2001 Posts: 5182

If you have many triggers that are open like #TR {*} then you will have this problem. Especially if those triggers preform a lot of proccessing. The best way to use such triggers is as a #CONDITION for another trigger. Only store the captured text during that trigger, then preform proccessing at a later time such as when your prompt comes up.

Other triggers that are composed mostly of wildcards take longer to match or fail. Since every active trigger is tested on every line you should always try to keep wildcard heavy triggers confined to be active only when they are likely to be matched. Again #CONDITION is a great way to do this, but you can also use #T+ and #T-.