[OpenLayers-Users] More than 20 wms layers, performance issues, geowebcache concurrency

[Sergeant_york]

Greetings,

Right now I am responsible to add more than 20 wms layers to a map
application. I cannot group wms layers in the serverside. Therefore I had 2
solutions as far as I could find.

1- Adding each layer as one openlayers.layer.wms: The problem is if you add
20+ wms layers to a map in openlayers, on the client side I see performance
issues (Browser uses too much memory and application works too slow). So I
decided to group the layers clientside...
2- Grouping layers clientside: I've grouped 20+ layers to 4-5 layer groups
with main titles such as "General -> Cities, Streets .. etc). This way
performance problem dissapeared but this time I realized Geowebcache which
was integrated to geoserver was not working. Therefore tiles were coming
from database server directly instead of cached tiles and that was so slow.
I used "mergeNewParams" method to group layers and to open/close their
visibility I simply removed layer from "layers" parameter.

So my question is:

I cannot add each layer as openlayers.layer.wms because of clientside
performance issues; I cannot group layers at clientside like "layers:
x,y,z...." since it doesn't trigger geowebcache. Is there any other option
to use to solve clientside performance issue and to be able to obtain tiles
from geowebcache?


Thank you for your answers,
Best regards



--
View this message in context: http://osgeo-org.1560.n6.nabble.com/More-than-20-wms-layers-performance-issues-geowebcache-concurrency-tp4991740.html
Sent from the OpenLayers Users mailing list archive at Nabble.com.