I think that all deployments in a J2EE container should use the connection pooling of the chosen container.
I do not see the importance of a change but perhaps I have overseen something. ? Andrea Aime writes: > Hi, > I've been experimenting a little with connection pools performance > and it seems the C3P0 connection pool > (http://sourceforge.net/projects/c3p0/) > is designed for slightly better scalability than the DBCP one we're > using today. > > In particular in a WMS request benchmark, and when reaching the high > number of clients (40 threads against a pool of 20 connections) the pool > provides a 5-10% speed increase over a, which is not so bad given it's > just a library change. > > I would like to add it to the mix, just not sure how. > Shall we replace DBCP? Or give people another option, a list of > supported pools that does include DBCP and C3P0? > > The current connection options are pretty much supported by both > pools, thought C3P0 has more configuration knobs to offer. For > example, the connection validation can happen in a background thread > as opposed to doing every time a connection is extracted from > the pool. > > If anybody wants to try it out against PostGIS I've attached a quick > test for the NG datastore to this mail (non definitive, the > real thing should be probably moved to the core JDBC module so that > every JDBC datastore is affected). > > Cheers > Andrea > > -- > Andrea Aime > OpenGeo - http://opengeo.org > Expert service straight from the developers. ------------------------------------------------------------------------------ Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day trial. Simplify your report design, integration and deployment - and focus on what you do best, core application coding. Discover what's new with Crystal Reports now. http://p.sf.net/sfu/bobj-july _______________________________________________ Geotools-devel mailing list Geotools-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/geotools-devel
