On Thu, Nov 11, 2010 at 12:48 PM, G. Allegri <[email protected]> wrote: > I have to set up a geoserver postgis datastore in a production > environment, and I was wondering about performance optimizations. > Coming to the connection pooling issue I read that Geoserver datastore > handles connection pooling configuration. My question are: > > - how does geoserver manage pooling?
DBCP, latest stable release (or close, we ugpraded it only a few months ago) > - would it be advisable to use an eternal pool, like tomcat DBCP? > Would it give us performance gain? None that I can think of. Storing the connection pool in JNDI is a good idea if you need to create multiple stores hitting the same database (each hitting a different schema), if you need to share the pool with other applications running in the same container, or if the standard connection setup cannot be used (e.g., connecting to an Oracle cluster). If you need better performance the easier way is to upgrade to GeoServer 2.1 beta (yes, that comes with some risks ;-) ) Cheers Andrea ----------------------------------------------------- Ing. Andrea Aime Senior Software Engineer GeoSolutions S.A.S. Via Poggio alle Viti 1187 55054 Massarosa (LU) Italy phone: +39 0584962313 fax: +39 0584962313 http://www.geo-solutions.it http://geo-solutions.blogspot.com/ http://www.linkedin.com/in/andreaaime http://twitter.com/geowolf ----------------------------------------------------- ------------------------------------------------------------------------------ Centralized Desktop Delivery: Dell and VMware Reference Architecture Simplifying enterprise desktop deployment and management using Dell EqualLogic storage and VMware View: A highly scalable, end-to-end client virtualization framework. Read more! http://p.sf.net/sfu/dell-eql-dev2dev _______________________________________________ Geoserver-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geoserver-users
