On 22/09/2010 17:10, Pedro Mendes wrote: > Hi, > > We had the same problem in my project. Two different approaches were taken: > > 1. We have many OL layers where the same geoserver featureType can be > referred by more than one OL layers (but with different SLD and > CQL_FILTER), so we aggregate the WMS requests to the same geoserver > featureType – this reduced the number of requests in 60%. > > 2. Our platform is accessed in a closed environment with IE, so it was > possible to recommend the registry update.
Mind there is a flipside: if the requests actually hit the WMS you might get out of memory or just poor performance in general (thrashing). That's why I developed the control-flow module: http://docs.geoserver.org/2.0.x/en/user/community/controlflow/index.html On the flipside, if you're hitting a tile cache there's another way to get around that issue, which is to using multiple domain names for your servers and tell OL to round robin the requests on those. See for example: http://wiki.openstreetmap.org/wiki/OpenLayers/FasterTiles Cheers Andrea -- Andrea Aime OpenGeo - http://opengeo.org Expert service straight from the developers. ------------------------------------------------------------------------------ Start uncovering the many advantages of virtual appliances and start using them to simplify application deployment and accelerate your shift to cloud computing. http://p.sf.net/sfu/novell-sfdev2dev _______________________________________________ Geoserver-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geoserver-users
