Links may not function; however, this content may be relevant to outdated versions of the product.
Tuning a requestor pool configuration
By using the Requestor Pools landing page, you can tune requestor pool configuration to ensure the most effective use of system resources. For example, you can resize a requestor pool to adapt to incoming demand on requestors.
To tune a requestor pool for a service package, analyze the pool metrics and modify threshold values for the requestor pool. By analyzing the metric, you can evaluate the requestor pool performance and identify possible bottlenecks.
For example, if the requestor pool is fully in use and no idle requestors are available, then a new incoming request waits for a requestor to become idle. After the maximum waiting time passes, the new request times out. In this situation, you might want to increase values of idle requestors and maximum wait according to the expected load.
To access the Requestor Pools landing page, view the list of requestor pools, view details about a requestor pool, and open a service package form, you must have the PegaRULES:SysOpsObserver role. To perform all available actions on requestor pools, for example, to clear a requestor pool, you must also have the PegaRULES:SysOpsAdministrator role.
- In the navigation pane of Admin Studio, click .
- Analyze the metrics for a requestor pool for which you want to tune the
configuration.The Requestor Pools landing page displays the following metrics:
- The number of requestors that are currently in the pool, available for use, and waiting for a service request.
- The number of requestors that are currently out of the pool, in use, and managing service requests.
- Longest wait time
- The longest time a service waited for a requestor to become available.
- The number of times the system timed out while waiting for a requestor to become available.
Values that are shown in red indicate potential issues and need to be reviewed:
- If the value for most active requestors exceeds the maximum active threshold that is configured for the requestor pool, the value for active requestors is displayed in red to indicate that a pool size needs to be increased.
- If the value for the longest wait time is above zero, the value is displayed in red to show that peak capacity has been reached.
- To analyze extended metrics and threshold values, click View
details for service package for which you want to tune a requestor pool. The Requestor pool details dialog box displays additionally:
- Most idle
- The greatest number of requestors that were idle at the same time.
- Most active
- The greatest number of requestors that were active at the same time.
- Maximum idle
- The threshold value configured for a requestor pool on the Pooling tab in the Service Package form. The threshold is the maximum number of idle requestors that are allowed in the requestor pool.
- Maximum active
- The threshold value configured for a requestor pool on the Pooling tab in the Service Package form. The threshold is the maximum number of active requestors that can be in use at the same time.
- Maximum wait
- The threshold value configured for a requestor pool on the Pooling tab in the Service Package form. The threshold is the maximum time that the system can wait for a requestor to become available (return to the pool) when the service is waiting but the maximum number of active requestors was reached.
- Modify the threshold values for a requestor pool that you want to tune.
- In the Service package column, click the service package name for which you want to tune a requestor pool.
- On the Pooling tab on the Service Package form, modify one or more of the threshold values: Maximum idle, Maximum active, Maximum wait.
- Optional: Clear a requestor pool.
Previous topic Requestor pooling for services Next topic Managing log categories