| 07-16-2008, 08:20 PM | #1 |
Ive seen lots of code and talk about speed on Trigger calling... Whats the real scoop on speed overhead etc comparing: I have a trigger that does more than just condition testing and then call it using.... TriggerEvaluate( t) vs TriggerExecute( t) ie. Is it better to call a condition to execute an action or just an action itself. Thanks! I have read various accounts but would like solid evidence of picking one over the other if such a thing exists. |
| 07-16-2008, 08:29 PM | #2 |
TriggerEvaluate won't run a trigger's actions, it will just evaluate the condition and return true or false. You still need TriggerExecute to run the actions. |
| 07-16-2008, 10:47 PM | #3 | |
Quote:
However that wasnt my ?... If you choose to actually use the condition AS your action then you dont need to TriggerExecute... Basically i have been told that evaluate runs faster than execute and since they are both just executing the same code why is evaluate faster? |
| 07-16-2008, 11:08 PM | #4 |
Evaluate doesn't create a proper thread (can't have waits in it). |
| 07-16-2008, 11:17 PM | #5 | |
Quote:
So if you dont have waits then use evaluate for faster.. but how much faster? |
| 07-16-2008, 11:37 PM | #6 |
~2 times. See the 'Evaluate and Execute speeds.' thread on the second page. |
