I agree that there is value in limiting what is rendered, but my current concern is whether what I'm seeing performance-wise indicates a problem in my GeoServer setup or is just normal behaviour. If there is an issue, and 130,000 should render quicker, then I might still see sub-optimal rendering even with 10,000 points. Perhaps the current data volume is helping to highlight an issue with my server that is less apparent at lower volumes.
Once I am have a clear idea what is going on I will look at reducing what is rendered. -- View this message in context: http://osgeo-org.1560.n6.nabble.com/5-seconds-to-render-130-000-points-typical-GeoServer-WMS-performance-tp4995984p4996232.html Sent from the GeoServer - User mailing list archive at Nabble.com. ------------------------------------------------------------------------------ Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ _______________________________________________ Geoserver-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geoserver-users
