Marcin Rudowski wrote:
>
> I discovered, that in my case biggest problems were style rules with
> high MaxScaleDenominator for very rare features mixed with popular
> ones with small MaxScaleDenominator in one layer.
Obviously, one could fix that by splitting up layers according to
MaxScaleDenominator. But isn't there a penalty for overdoing this, too? If I
increase the number of layers/SQL queries too much, I would assume that
thingsslow down. Does anyone have a rule of thumb for this?
thanks
Nop
--
View this message in context:
http://n2.nabble.com/Performance-considerations-tp4508868p4525003.html
Sent from the Mapnik Users mailing list archive at Nabble.com.
_______________________________________________
Mapnik-users mailing list
[email protected]
https://lists.berlios.de/mailman/listinfo/mapnik-users