Connection pool settings
Pega Platform is an application requiring a high database connection request and return rate. In Pega Cloud environments, Pega manages the connection pool settings across the fleet of systems that are appropriate for the range of client’s business needs, based on our experience. Pega Cloud clients cannot change or request changes to the default configuration.
For on-premises clients, to ensure that your data is persisted throughout any period of intensive database processing, Pega recommends using the following connection pool settings (on a per node basis) during the Pega Platform installation process, as described in the Installation and Update Guides:
Connection pool default settings
| Per node setting | Recommendation |
| Initial Pool Size | 0 |
| Minimum Pool Size | 3 |
| Maximum idle connection count | 25 |
| Maximum Pool Size | 75 |
| Connection Validation Strategy | Test upon requesting any connection. |
| Connection Validation Method | Use the JDBC4 driver’s default validation method (isValid() API) instead of a providing a specific validation SQL. Pega recommends this approach to minimize connection pool changes as database vendors provide updates to either their products or drivers. It also ensures that the pool is configured to use the vendor’s best practice for validating the connection. |
| Idle Connection Eviction Policy | Enabled |
| Eviction Thread Run Frequency | 5 seconds |
| Idle Connection Timeout | 1 minute |
| Connection Creation Wait Timeout | 10 seconds |
These settings will allow most clients’ database connections to maintain stability and scale up or down in line with the end users and processes that are running on most client systems. Pega recommends starting with a relatively high maximum pool per node, to be able to handle high usage, a low idle timeout per node for prompt eviction, a low minimum pool per node to avoid database connection overhead during quite periods, and a reliable connection validation.
If an on-premises client's organization or specific database vendor software version recommends settings that conflict with these recommendations, a database administrator from your organization should reach out to your Pega representative to manage these settings before you install Pega software.
Previous topic Understanding the database structure Next topic Custom connection properties required for disaster recovery