 |
Fredd
Newbie
Joined: 08 Feb 2003
Posts: 5
Location: United Kingdom
|
 Posted: Fri Aug 13, 2004 6:38 am
zMud processing speed.
|
I've just realised how much all my settings in zMud are slowing everything down. I never realised how many things I had added until I counted recently and found I have 420 triggers and 300+ aliases! The ctrl-q command is giving me a score of almost 60. Apart from stripping out some of the unnecessary stuff I have some questions about speeding up my setup. (I'm using zMud 7.05)
When pattern matching should I use the minimum amount of matching text or as much as I can, the whole line for example?
7.05 converts the triggers into regular expressions internally. Would converting all my triggers into regular expressions (with the convert button in settings editor) speed things up?
I read that a "bad trigger" can cause a lot of lag, but what makes a bad trigger?
Also saw advice recommending that you put the entire script into the trigger rather than having it call an alias that executes the next part of the script. Why would this be faster and would it mean my large number of aliases could also be having an impact on speed?
Any other tips?
Thanks. |
|
|
|
|
LightBulb
MASTER
Joined: 28 Nov 2000
Posts: 4817
Location: USA
|
Posted: Fri Aug 13, 2004 5:59 pm Re: zMud processing speed.
|
| Quote: |
When pattern matching should I use the minimum amount of matching text or as much as I can, the whole line for example?
|
For fastest processing, use as much SPECIFIC (verbatim) text as you can without adding wildcards.
| Quote: |
7.05 converts the triggers into regular expressions internally. Would converting all my triggers into regular expressions (with the convert button in settings editor) speed things up?
|
Obviously yes, but only slightly. zMUD only does the conversion once, then keeps the converted pattern in memory, so the speed improvement would only come the first time the trigger is checked.
| Quote: |
I read that a "bad trigger" can cause a lot of lag, but what makes a bad trigger?
|
One that causes a lot of lag, of course!  Some examples:
a. Loops (#LOOP, #FORALL, etc)
b. #WAIT
c. Patterns that match almost every line
d. Patterns that span several lines, using the $ symbol
| Quote: |
Also saw advice recommending that you put the entire script into the trigger rather than having it call an alias that executes the next part of the script. Why would this be faster and would it mean my large number of aliases could also be having an impact on speed?
|
It would be faster because it saves a step.
The number of aliases isn't likely to be a problem.
I already explained all this in detail in the post to Yodous (the one where you saw all these recommendations). It doesn't change just because you ask the same questions again. Loops and #WAIT cause the most lag, the rest is likely to make little or no noticeable difference. |
|
_________________
LightBulb
Senior member
Most scripts in this forum are written for Command Line entry.
Don't even open the Settings Editor unless its use is specified or obvious. |
 |
|
|
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
