Hi Sergey, Before writing your own renderer code you might want to look at CachingFeatureSource. Perhaps it will give you the performance boost that you need.
http://docs.geotools.org/stable/javadocs/org/geotools/data/CachingFeatureSource.html Michael On 12 July 2011 20:18, LSA <[email protected]> wrote: > Is it hard to implement GTRenderer interface? What can be said about it? > > Standard renderer used is StreamingRenderer, and comments in the source code > say this: > Use this class if you need a stateless renderer that provides low memory > * footprint and decent rendering performance on the first call but don't > need > * good optimal performance on subsequent calls on the same data. > > I am in quite opposite situation: I can sacrifice some memory in order to > gain performance. > > Did someone tried to implement GTRenderer which will have better performance > on subsequent calls on the same data? > > Thanks, > Sergey > > ------------------------------------------------------------------------------ > All of the data generated in your IT infrastructure is seriously valuable. > Why? It contains a definitive record of application performance, security > threats, fraudulent activity, and more. Splunk takes this data and makes > sense of it. IT sense. And common sense. > http://p.sf.net/sfu/splunk-d2d-c2 > _______________________________________________ > Geotools-gt2-users mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/geotools-gt2-users > > ------------------------------------------------------------------------------ All of the data generated in your IT infrastructure is seriously valuable. Why? It contains a definitive record of application performance, security threats, fraudulent activity, and more. Splunk takes this data and makes sense of it. IT sense. And common sense. http://p.sf.net/sfu/splunk-d2d-c2 _______________________________________________ Geotools-gt2-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geotools-gt2-users
