Resolution:
Description:
===========
CPU usage increases to 95% while invoking decision tables in TIBCO BusinessEvents .

Environment:
===========
TIBCO BusinessEvents 4.x , 5.x
All Operating Systems

Symptoms :
===========
Task and Process Monitoring tools shows CPU usage to exceed 95% usage on invoking Decision Tables .

Cause :
===========
The actual cause depends on the product usage . However a few ways to reduce the CPU consumption is described in the section below .

Resolution:
===========
Potential causes and resolutions to minimise CPU usage while using decision tables .

1). Check for Decision Tables which have no conditions but have action that does RuleFunction invocations. Replace the calls to these Decision Tables with the respective RuleFunction invocations.

2). Identify the Decision Tables which has rules with duplicate conditions and combine them into one rule.

3). Identify if there are multiple invocations of of a RuleFunction from the respective decision table. Depending on the usage of the rule function if the RuleFUnction creates a ontology object inside it then multiple invocations could create multiple ontology objects. The logic could be tuned to involve a single invocation which runs the above process although the usage may vary with each project .

4). Bring down the System.debugOut() calls - Remove the action columns having System.debugOut() calls.

CPU usage increases to 95% while invoking decision tables in TIBCO BusinessEvents .