font files aren't loaded unless explicitely used in the map rendering.<br>lazy loading of images is on my todo-list with the rendering api (if only because they are loaded through GD right now, and this would need to be changed)<br>
<br>regards,<br><br>thomas<br><br><div class="gmail_quote">On Sat, Nov 21, 2009 at 17:03, 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;">
In my case I have a lot of symbols that are never used on render<br>
request because of 2 reasons:<br>
1) There are a lot of layers(~20) and they need to be delivered in<br>
real time (so no tile cache or 1 wms request per layer) thats why all<br>
layers are rendered at server side as 1 image. Thats why I can't use<br>
multiple symbolsets.<br>
2) An example of one of this layers is Fire hydrants, based on<br>
attributes I have 12 different types of them (12 images)<br>
<br>
I fully understand that my case is not common. Are there are ways to<br>
solve this problem not sacrificing a lot of performance like opening a<br>
lot images and font files on every request ? I think it's a nice<br>
example of what benefits we can is some cases from lazy-loading.<br>
<div><div></div><div class="h5"><br>
On Sat, Nov 21, 2009 at 3:55 PM, thomas bonfort<br>
<<a href="mailto:thomas.bonfort@gmail.com">thomas.bonfort@gmail.com</a>> wrote:<br>
> Pavel,<br>
><br>
> On Wed, Nov 18, 2009 at 13:24, Pavel Iacovlev <<a href="mailto:iacovlev.pavel@gmail.com">iacovlev.pavel@gmail.com</a>><br>
> wrote:<br>
>><br>
>> 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).<br>
><br>
> recent versions of mapserver aren't limited to 64 symbols anymore.<br>
><br>
>> 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.<br>
><br>
> lazy loading of symbols would definitely make sense for image symbols,<br>
> although only for people with a single symbolset for multiple instances, as<br>
> 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<br>
> this is only a parser operation that has to be done anyways.<br>
><br>
>><br>
>> Another question is if I have<br>
>> 100 image symbols all 100 images are loaded into memory on render<br>
>> request ?<br>
><br>
> yes, all the image files are loaded.<br>
><br>
> regards,<br>
><br>
> thomas<br>
><br>
><br>
<br>
<br>
<br>
</div></div><div><div></div><div class="h5">--<br>
<a href="http://iap.md" target="_blank">http://iap.md</a>, The future is open<br>
</div></div></blockquote></div><br>