Hi Ian, Thanks again, yes we are using 4x4 meta tiling.
It isn't specifically access to the DB that is the bottle neck, as we use tiled requests it sends an inordinate amount of requests to the DB server. The turn-around for a single request is not too bad at all (3-4ms) and our DBA assures us that the query plan is as good as it can be. It is more a matter of when we increase the number of requests on the DB it just generates a mass backlog of queries to process. Something that is only going to get worse as we ramp up. Instead we have the option of using single tile (full screen) map requests which will reduce the traffic to the DB but will inherently hit performance on the front end and GeoServers by increasing rendering time. I do have GWC configured to cache on request too, hopefully that will reduce some of the load. regards -- View this message in context: http://osgeo-org.1560.x6.nabble.com/OS-Mastermap-in-Production-1000-s-of-users-tp5213560p5213748.html Sent from the GeoServer - User mailing list archive at Nabble.com. ------------------------------------------------------------------------------ Don't Limit Your Business. Reach for the Cloud. GigeNET's Cloud Solutions provide you with the tools and support that you need to offload your IT needs and focus on growing your business. Configured For All Businesses. Start Your Cloud Today. https://www.gigenetcloud.com/ _______________________________________________ Geoserver-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geoserver-users
