Hi! Yes, Andreas, you are right. We use so many LAYERs because of transparencies: Mapserver (maybe every GIS) cannot deal overlapping geometries in different CLASSes inside the same LAYER; without a proper analisys of data we had no choice: write a LAYER per CLASS.
The result is not reasonable (too slow), so now a colleague of mine is performing such a (long) data analisys. Another bad practice of mine has been stuffing all of such LAYERs inside a single mapfile: this explains why the server is so slow in creating a response for GetLegendGrapghic (from 2s to 4s!!!). Now I'll separate LAYERs in a few different mapfiles, so I expect another little performance boost. Last but not least, I'm looking for a cacheing mechanism in the web server: maybe Apache is enough for that. As usual, problems teach you a lot more :-) Thank you very much for you help! Regards, Vito ----- Messaggio originale ----- Da: "Andreas Hocevar" <[email protected]> A: "Vito Meuli" <[email protected]> Cc: "GeoExt Users" <[email protected]> Inviato: Martedì, 11 maggio 2010 18:08:22 GMT +01:00 Amsterdam/Berlino/Berna/Roma/Stoccolma/Vienna Oggetto: Re: [Users] Fwd: GeoExt.LegendPanel too slow with too many sublayers Hi, everything I see in your demo works as expected. Your servers, however, respond very very slowly. Your sublayers are not exposed to the layer tree. I see you are using Mapserver. Why don't you just create CLASSes instead of LAYERs for e.g. road categories? Regards, Andreas. _______________________________________________ Users mailing list [email protected] http://www.geoext.org/cgi-bin/mailman/listinfo/users
