Bookshelf Home | Contents | Index | Search | PDF | ![]() ![]() ![]() ![]() |
Performance Tuning Guide > Tuning Siebel Workflow for Performance > Tuning Workflow Policies for Performance >
Performance Tuning Tips
The following are some tips to improve performance:
- 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.
- Too many records indicate that the number of workflow policies monitored is too large. In this case, add more 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.
NOTE: Maintain the S_ESCL_REQ, S_ESCL_ACTN_REQ, and S_ESCL_STATE tables by adjusting storage, access, and cache related parameters. Refer to the database documentation for additional information on properly adjusting these table parameters. Also, make sure the database administrator (DBA) is aware of these key tables.
- Run multiple Workflow Monitor and Workflow Action Agents in parallel. Doing so:
- Distribute workflow policy processes across Siebel Servers. You can distribute processes so that:
- If you find that Workflow Policies runs significantly slower during a certain time period, investigate what other processes may be contending for CPU resources on the Siebel Server. You may discover that the Siebel 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 Siebel Servers so that the polling periods are compatible with the resources available.
Bookshelf Home | Contents | Index | Search | PDF | ![]() ![]() ![]() ![]() |
Performance Tuning Guide Published: 24 October 2003 |