Idle requestor and active requestor depends on one another, Ex: 15 request and idle requestor= 3 and Active requestor configured=10.
pega will first re-use active requestor and create 7 new requestor for processing and again all these 10 will move back to idle and then again 5 requestor will be re- used from idle.
As it is recommended in pega that "never set Maximum idle requestors size higher than Maximum active requestors. Requestors remain unused in idle pool if an idle requestor value exceeds active requestor value."
Please explain "Requestors remain unused in idle pool if an idle requestor value exceeds active requestor value." , ??
@ADITIJ49 In Pega, requestor pooling helps reuse requestors (temporary instances used for processing tasks) to improve performance. The idle requestor pool holds requestors that have completed their tasks and are waiting to be reused, while active requestors are those currently handling tasks. If the idle requestor pool size exceeds the active requestor limit, the extra idle requestors remain unused because Pega only reuses up to the configured number of active requestors. For example, if 10 active requestors and 15 idle requestors are configured, only 10 requestors will be reused, and the remaining 5 will stay unused in the pool. This can lead to wasted resources since those extra idle requestors occupy memory without contributing to task processing. Therefore, Pega recommends keeping the idle pool size equal to or lower than the active pool size to avoid unnecessary resource consumption and ensure efficient requestor management. By matching the idle pool with the active pool, you can ensure optimal performance without resource wastage.