Configure a JDBC connection pool
Performance Testing Service (PTS) uses the open source Druid library to manage Java Database Connectivity (JDBC) connection pools. A connection pool reuses database connections across JDBC requests, reducing connection establishment overhead during load tests.
Prerequisites
Before you begin, make sure that you have:
Configured the basic request information of a JDBC API. For more information, see Basic request information
Configure connection pool parameters
In the JDBC API configuration section, click the Connection Pool Settings tab.
Set the following parameters.
Parameter
Description
Example
Initial Connections
The number of physical connections created when the pool initializes. A higher value speeds up early test requests but increases startup time.
1
Max Connections
The maximum number of active connections the pool can hold. When all connections are in use, new requests wait until a connection is released or the wait time expires.
500
Min Connections
The minimum number of idle connections kept in the pool. Druid maintains at least this many connections even when they are not actively used.
1
Max Wait Time
The maximum time, in milliseconds, to wait for an available connection. If no connection becomes available within this period, the request fails with a timeout error.
4000