Pavel,<br><br><div class="gmail_quote">On Wed, Nov 18, 2009 at 13:24, Pavel Iacovlev <span dir="ltr"><<a href="mailto:iacovlev.pavel@gmail.com">iacovlev.pavel@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Good day all,<br>
<br>
As I understood on render request mapserver loads all symbols into<br>
memory thats is fine if you have under 64 symbols (default limit). </blockquote><div><br> recent versions of mapserver aren't limited to 64 symbols anymore.<br><br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
I<br>
have a topographical map to render that maybe will have around 200+<br>
symbols and like 5-10 will be used per request. Maybe implementing<br>
lazy-loading (only then needed) for symbols will improve the<br>
performance ? and remove the cap at all. </blockquote><div><br>lazy loading of symbols would definitely make sense for image symbols,
although only for people with a single symbolset for multiple
instances, as otherwise the case is rarer to have defined a symbol but
never use it.<br>
<br>
the other symbol types wouldn't see much benefit from lazy loading
imho, as this is only a parser operation that has to be done anyways.<br> </div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Another question is if I have<br>
100 image symbols all 100 images are loaded into memory on render<br>
request ?<br></blockquote><div><br>yes, all the image files are loaded.<br><br>regards,<br><br>thomas<br></div></div><br>