Mike Bresnahan ha scritto: > On 7/10/08, Jody Garnett <[EMAIL PROTECTED]> wrote: >> Yes clipping is probably more expensive then dealing with more content; you >> may want to pre-process your data (splitting along tile devisions) prior to >> servering it up via geoserver? > > I have tried this and was able to get almost a 2x performance improvement, > however it took 90 minutes to preprocess one layer using > java.awt.geom.Area.intersection(). > I was also surprised I only got a 2x performance improvement by tiling > the dataset. A typical > polygon in the dataset has 40,000 vertices. GeoServer seems to handle the > large > polygons much better than java.awt.geom.Area.intersection(). However, > ultimately the > performance is no where near the performance of serving up > prerendered/pretiled images > or polygons.
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 ------------------------------------------------------------------------- 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
