@ClaudiaH8392

Pega does manage requestor pooling which can be seen as a form of buffering to support transactionality. The requestor pool is a set of requestors reserved for use by the services in the Service Package which helps improve the performance of a service by enabling requestor reuse sharing allocated resources and eliminating server wait time for requestor creation. Your configuration of the service package for Mobile integration with the specified pooling settings (Maximum idle requestors as 20 Maximum active requestors as 300 Maximum wait as 15 seconds) is indeed related to this concept. These settings help manage the load and ensure that there are enough requestors available to handle the incoming transactions efficiently.

⚠ This is a GenAI-powered tool. All generated answers require validation against the provided references.

Configuring a requestor pool for a service package

Managing requestor pooling for a mobile app