What to know about intialization and warm-up behavior of BES Jdbc connection pool ?
BES Jdbc pool lazily creates Jdbc connections. In other words, new connections are only created when application needs them. In a long running server application this cost amortizes overtime,. Typically benchmarks have a way to warm-up/rampup your serve. So, it is important to do that with the same stress/concurrency level as expected in the steadyState (ie measured interval). This is specially true in SPECjAppServer200x (ECperfTM) benchmarks. As BES doesn’t provide initSize(), the very first request to get Jdbc connection will be expensive, as it involves two (one-time) RPCs • A JNDI lookup (of the vendor datasource) which may involve an RPC if naming service is not running within your partition. This is per datasource lookup. • An RPC to the database to create a new connection. This is for each new connection created.
