Re: [Geotools-devel] Screenshot of the 'renderer' module

[Andrea A. <aa...@li...>]

Martin Desruisseaux wrote:
> Andrea Aime wrote:
> 
>> Now, the only things that keeps me from dropping the lite renderer
>> is memory usage and the inability to deal with sld.
> 
> 
> SLD is an important issue. Unfortunatly, I will be unable so solve this 
> one alone. I hope it will come progressively as contributors put some 
> code in RenderedLayerFactory.

Will think about it ;-)

[SNIP]
> 
>> Does it make sense to use a stateful renderer in the wms context, when 
>> you
>> are serving potentially dozen of maps?
> 
> 
> It is better to have one Renderer by map, which means a dozen of 
> renderers here... Note that Renderer has a 'dispose()' method which free 
> imediately all resources. A wms could handle for example a maximum of 5 
> Renderers in same time. If a new Renderer is required, then the oldest 
> one could be disposed and recreated later if it is needed again. Of 
> course this disposal/recreation work add CPU overhead. This is a 
> memory/speed tradeoff.

Yes, I see... yes, a Renderer pool could be

> I think that a stateless Renderer would be similar in performance to 
> using only one stateful renderer and disposing/recreating it all the time.

Uhm, probably not, the stateless renderer (lite renderer) doesn't need to create
RenderedFeatures, using directly the geometry thru wrappers, so it should
produce way less garbage. I think some testing is needed, but first
someone have to provide sld compliance to you renderer... I'm tempted...
We will see how much spare time I get once the university course is finished
(one more week).

Andrea