> Have you run the rendering inside a profiler and the actual draw part > resulted the be the bottleneck, or you're just assuming it is? > Data loading could be your bottleneck > Cheers > Andrea >
Yes I did, but I did it more to trace the code execution than to understand where the performance bottlenecks were. However, I did notice a majority of the time was spent querying the data. I have a working prototype of my app that caches the resultant images rendered by GeoServer, but I have been exploring ways to speed up the pre-render step and alternative architectures that use less network bandwidth by sending vectors to the client instead of rasters. I thought I would get big GeoServer rendering gains by pre-tiling the data, but I have only been able to get a 2x increase. This increase does not make up for the time spent pre-tiling the data, nor does it make real-time rendering feasible. Most recently I have been playing with the Sutherland-Hodgman polygon clipping algorithm. Preliminary results suggests it is blindingly fast compared to Area.intersection which I am guessing is using a variant of Weiler-Atherton. ------------------------------------------------------------------------- Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW! Studies have shown that voting for your favorite open source project, along with a healthy diet, reduces your potential for chronic lameness and boredom. Vote Now at http://www.sourceforge.net/community/cca08 _______________________________________________ Geotools-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geotools-devel
