WAS v8.5 > Tune performance > Tune Data access resourcesTune data
Subtopics
- Tune connection pools
Using connection pools helps to both alleviate connection management overhead and decrease development tasks for data access. Each time an application attempts to access a backend store (such as a database), it requires resources to create, maintain, and release a connection to that datastore. To mitigate the strain this process can place on overall application resources, the application server enables administrators to establish a pool of backend connections that applications can share on an application server. Connection pooling spreads the connection overhead across several user requests, thereby conserving application resources for future requests.- Throttling inbound message flow for JCA 1.5 message-driven beans
This topic describes how to throttle message delivery for message-driven beans (MDB) which are deployed as message endpoints for Java EE Connector Architecture (JCA) v1.5 inbound resource adapters.- Database performance tuning
Database performance tuning can dramatically affect the throughput of the application. For example, if the application requires high concurrency (multiple, simultaneous interactions with backend data), an improperly tuned database can result in a bottleneck. Database access threads accumulate in a backlog when the database is not configured to accept a sufficient number of incoming requests.- Data access tuning parameters
For better application performance, we can tune some data access resources through the WebSphere Application Server dmgr console.- Directory conventions
References in product information to app_server_root, profile_root, and other directories imply specific default directory locations. This article describes the conventions in use for WAS.