Feature Priority: Normal
Feature Impact: Huge for Scripters

Triggers are an ongoing discussion. The scripters start to replace the "bad loops" with "good triggers". It would be great to create analyzation tools for code performance tracking like:

• Loop detection:

-> Log down recurring code executions and evals
-> Log down the statement evaluation execution time of loops, triggers, waituntil and the well known bad guys
-> Log down the average number of statement evals per second or minute
-> Log down the average time for evaluating looped conditions per second or minute
to visualize the impact.

Please consider to log them down into a delimited format, which can be identified and separated. Or in arrays in namespaces.

The feature needs to be activated / deactivated with a client / server debug or developement parameter, because itself will cost performance.

The parameter could improve the overall script performance with the correct announcments and maybe script solution challenges.