Yukka: unfortunately yes, at this point it is necessary to draw all the points. I have to show their distribution so I can't hide some and show others as it would misrepresent the overall shape. As their locations frequently change it is not feasible to calculate any of this in advance and calculating on the fly would presumably incur a higher performance cost.
However, even if I could reduce the number of points displayed the performance question - and whether this is typical - still stands. cholmes: I might be able to try this, or test with a Shapefile, but Oracle is already in place as the operational database and there is no scope to change it. Do you have any suggestions on where I might find more information about these bottlenecks? Also I'm a bit confused about how Oracle would affect rendering performance if what I think it happening is true - after Oracle finds all the data it takes GeoServer 5 seconds to display it and Oracle does very little until the connection is closed - am I missing something here? Thanks both for your input -- View this message in context: http://osgeo-org.1560.n6.nabble.com/5-seconds-to-render-130-000-points-typical-GeoServer-WMS-performance-tp4995984p4996023.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
