Bookshelf v7.5: Performance Tuning Tips

Siebel Business Process Designer Administration Guide > Monitoring and Tuning Performance > Tuning Workflow Policies for Performance >

Performance Tuning Tips

The following are some tips for dealing with common performance problems:

Monitor the size of S_ESCL_REQ and S_ESCL_STATE tables.

If these tables are too large, they may slow down your system's performance.

In general:

Too many records indicate that the number of workflow policies monitored is too large. In this case, add additional Workflow Agents to handle the load.

If rows are not removed after the time interval is met, the workflow policy may have been deactivated but the triggers were not removed. These tables will become very large if you do not restart Generate Triggers.

Run multiple Workflow Monitor and Workflow Action Agents in parallel. Doing so:

Focuses an agent's polling resources on a smaller number of workflow policies.

Allows faster throughput by shortening the time between when the workflow policy event is triggered and when the agent notices the event.

Distribute workflow policy processes across Siebel Servers. You can distribute processes so that:

High-maintenance policies can be grouped on a server with sufficient resources to handle the workflow CPU requirements.

Low-maintenance policies can be run on a server that shares resources with other Siebel processes.

If you find that Siebel Workflow Policies runs significantly slower during a certain time period, you should investigate what other processes may be contending for CPU resources on the Siebel Application Server. You may discover that the server has certain time periods with high activity that interfere with the ability of the Workflow Policies process to monitor or act. Arrange the Workflow Policies processes on the servers so that the polling periods are compatible with the resources available.