|
ReedN Wizard
Joined: 04 Jan 2006 Posts: 1279 Location: Portland, Oregon
|
Posted: Thu May 11, 2006 9:00 pm
System slowing down with many triggers |
I've now got a ton and a half of triggers and things are slowing way down. What things with triggers slows them down the most?
1) How does having multi-line triggers affect speed?
2) Does putting a ^ at the beginning of the line help it speed up a little? From my way of thinking it should because it just has to try matching at the beginning of the line instead of at any location in the line.
Has anyone found ways to seed up their triggers or things to avoid that help with speed?
Thanks,
-Reed |
|
|
|
Vijilante SubAdmin
Joined: 18 Nov 2001 Posts: 5182
|
Posted: Thu May 11, 2006 11:37 pm |
Multiline triggers are bad, but not really all that much worse then a regular trigger.
Adding the caret will certainely help, also ticking the case option helps. Anything and everything you can do to narrow down the possible matches for most of your triggers will help.
The best suggestion I can possibly give is take advantage of Zugg's offer to upgrade current purchases of zMud to CMud, then wait for CMud. I believe Zugg plans to implement an idea I had that will improve trigger matching speed, and the overall script speed gains Zugg has reported in his early testing are a huge improvement over zMud. Definitely worth buying. |
|
_________________ The only good questions are the ones we have never answered before.
Search the Forums |
|
|
|
Zhiroc Adept
Joined: 04 Feb 2005 Posts: 246
|
Posted: Fri May 12, 2006 1:14 pm |
One thing I do a lot of is to keep triggers disabled when the output they work on is generated only when you execute a certain command. So I create a command input Trigger that enables a class or is a multi-state trigger, then disable/reset to the initial state when done.
|
|
|
|
|
|