Ok, that's nice :) We must make sure that this is switched on in the ConnectionFactory which creates and configures the commons-DBCP pool.
Best regards Martijn > -----Original Message----- > From: Jukka Zitting [mailto:[email protected]] > Sent: Wednesday, September 09, 2009 10:12 AM > To: [email protected] > Subject: Re: JCR 1456 Database connection pooling > > Hi, > > On Wed, Sep 9, 2009 at 9:59 AM, Martijn Hendriks<[email protected]> wrote: > >> Agreed, though intuitively the effect of pooling should be > negligible > >> (a few extra method calls and hash lookups compared to the work that > >> happens in the underlying database). > > > > Well...also the cached PreparedStatements from e.g. the BundlePMs > have > > been removed (the ConnectionRecoveryManager maintained that cache). > > That might just have a more significant effect on performance. > > DBCP also pools prepared statements, so even there the effect should > be minimal. Other connection pools that don't do this might see a hit, > but that's easily worked around by replacing the pool with DBCP. > > BR, > > Jukka Zitting
