Optimizing the classic rule engine

Optimize the performance of the classic rule engine through the RetePlus, sequential or Fastpath execution mode, and configure the engine for execution.

Autoboxing
Autoboxing options convert primitive types to the corresponding wrapper types, and conversely. Autoboxing is enabled by default but you can disable it. Some wrapper instances are cached for better performance. Autoboxing and value caching affect the working memory.
Running several rule engines in parallel
Avoid using the same objects in different engines in different threads. Several engines can share the same ruleset.
Adjusting conditions
Most of the execution time is taken up by the pattern-matching process. Consequently, the most efficient way of improving performance in rulesets consists in modifying the condition part of rules.
Improving the performance of the RetePlus execution mode
You can improve performance by avoiding certain operations in the RetePlus execution mode.
Improving the performance of the sequential execution mode
You can improve performance of the sequential execution mode by setting up optimization levels or ratios, optimizing the caching, or setting the costly property. You can also reduce memory consumption.
Improving the performance of the Fastpath execution mode
You improve the performance of the Fastpath execution mode by modifying the condition part of rules.
Configuring the classic rule engine
You can use a configuration resource and configuration properties to set up the rule engine for execution.
Executing a rule task directly
When ruleflow performance becomes poor, you can use a specific API, known as rule task runners, for better control of rule tasks. Rule task runners work in RetePlus and in sequential execution modes. Use the provided code samples to write your own basic or dynamic rule task runners.

Parent topic: Optimizing execution