Planner Rule Profiling

---

$PLANNER_RULE_PROFILING

Some Notes

• This report was generated by utilizing Debugger.Event that the planner generated.
• Event profiling gives an overview over time spent with respect to general planner infrastructure.
• Planner rule profiling gives an overview over time spent with respect to specific rules invoked by the planner.
• All items not listing out times are invoked by the planner with a specific Location. These events are just counted.
• All items listing out times are invoked by the planner with location called BEGIN and END. These events are always sent in pairs. The time displayed is accumulated time spent between an occurrence of BEGIN and its corresponding END event.
• As BEGIN and END events can be nested we make a distinction between total time and own time which is akin to what normal profilers offer. Here are some known nestings:
  • All rules times add up to the times in TransformRuleCallEvent .
  • TransformRuleCallEvent nests within TransformEvent. This corresponds to trying all possible pre-patterns on a rule. The rule is then invoked per matching pre-pattern.
  • InsertIntoMemoEvent nests within TransformRuleCallEvent. This also means that the time spent to insert into the memo structure is subtracted from the own times of all planner rules.