Data access tuning parameters
For better application performance, you can tune some data access resources through the WebSphere® Application Server administrative console.
Tune these properties of data sources and connection pools to optimize the performance of transactions between your application and datastore.
Data source tuning
To view the administrative console page where you configure the following properties, click .- Enable JMS one phase optimization support
- If your application does not use JMS messaging, do not select this option. Activating this support enables the Java™ Message Service (JMS) to get optimized connections from the data source. Activating this support also prevents JDBC applications from obtaining connections from the data source. For further explanation of JMS one phase support, see Sharing connections to benefit from one phase commit optimization in this documentation.
- Statement cache size
- Specifies the number of statements that can be cached per connection. The WebSphere Application Server data source optimizes the processing of prepared statements and callable statements by caching those statements that are not being used in an active connection. Both statement types help reduce overhead for transactions with backend data.In general, the more statements your application has, the larger the cache should be. Be aware, however, that specifying a larger statement cache size than needed wastes application memory and does not improve performance.
- A prepared statement is a precompiled SQL statement that is stored
in a
PreparedStatement
object. Application Server uses this object to run the SQL statement multiple times, as required by your application run time, with values that are determined by the run time. - A callable statement is an SQL statement that contains a call
to a stored procedure, which is a series of precompiled statements
that perform a task and return a result. The statement is stored in
the
CallableStatement
object. Application Server uses this object to run a stored procedure multiple times, as required by your application run time, with values that are determined by the run time.
- A prepared statement is a precompiled SQL statement that is stored
in a
Connection pool tuning
To view the administrative console page where you configure the following properties, click .- Maximum connections
- Specifies the maximum number of physical connections that can be created in this pool. These are the physical connections to the backend datastore. When this number is reached, no new physical connections are created; requestors must wait until a physical connection that is currently in use is returned to the pool.
- Minimum connections
- Specifies the minimum number of physical connections to maintain. Until this number is exceeded, the pool maintenance thread does not discard physical connections.