Hi Anton,
If you are using Apache Tomcat or another container I recommend using
JNDI connection pooling. That way you have 1 connection pool shared
among all of your layers and you can manage it easily. I observed
significant performance gains when switching from "PostGIS" to "PostGIS
(JNDI)" type of store (database connections don't have to be recreated
with each request and it saves a lot of time). It works with ImageMosaic
datastores with custom dimensions too.
http://docs.geoserver.org/stable/en/user/tutorials/tomcat-jndi/tomcat-jndi.html
Cheers,
Peter
On 28. 9. 2016 8:57, Anton Lundkvist wrote:
Hi GeoServer Users:
I'm using GeoServer for serving vector data (from PostGis). Keeping
the number of stores down e.g. many layers per store reduces the
number of connections to PostGis. This is desirable as I have hundreds
of tables that are published through GeoServer.
Is there a recommended limit for how many layers / resources I should
handle with one store?
Regards,
Anton Lundkvist
------------------------------------------------------------------------------
_______________________________________________
Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users
--
Peter Kovac
IMS Programmer
MicroStep-MIS
peter.ko...@microstep-mis.com
------------------------------------------------------------------------------
_______________________________________________
Geoserver-users mailing list
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users
