Hi cheesybiskuits, Intriguing question. Obviously you are not using the WMS to produce a map but to see some pattern. I did a brief test using my desktop and our production Geoserver instance using a hydrology dataset with 370,000 points.
Sorry I cannot display that here as a table. However: Resolution steps: Scale 1000 points 7 M 370 4 M 120 2 M 35 925K 10 426K 3 231K 1 I.e. from 7M scale and 370,000 points down to 231K and 1000 points. The machines I compared are: Desktop: WinXP, Intel E8400, 3.00 GHZ, 3.21 GB Ram and WMS server: Windows 2008 R2, 64-bit, Intel Xeon, X5675, 3.06, 6GB RAM (virtual server, 3 cores assigned, i.e. half a physical CPU) So, my not so brilliant desktop against a blade server. both go to the same database ArcSDE 9.3 on Oracle. GeoServer is 2.1.3 (standard non-native JAI) and one is obviously 32-bit, the other 64. The performance overall is the same. The differences miniscule. server desktop 26.2sec 29.2sec 12.4sec 14.4sec 6.3sec 7.5sec 3.7sec 4.2sec 3.3sec 3.4sec 2.4sec 2.6sec I did 5 runs with very little differences between the values. It seems throwing hardware at the problem does not help. O.k. I didn't delve into puzzling the times apart using the Oracle and SDE logs. But there is something else that is a reason for concern: the linear increase if you look into the times. If you compare the numbers from the bottom up, the system seems to become faster per record at the beginning. As it should. From the scale 925K to 7M the increase seems linear with the amount of records, mind you the number of records usually quadruples. Databases are designed not to have a linear increase with increasing number of records. That is why they have indices, but from a certain amount the I/O becomes the limiting factor. The limit where this behaviour changes seems to coincide with your steps of 70K and 130K points. Same experience here with numbers even worse, uuuhm not so good. That brings us back to the beginning. You are not using Geoserver to produce a map but to quickly visualise and analyse a pattern and that seems only to work to a certain point. Whether Geoserver should cater for that, I do not know. That is a question for the community. Cheers Christian ----- ____________________________ Dr Christian Maul Project Manager Information Services Branch Department of Sustainability and Environment Level13, Marland House, 570 Bourke Street Melbourne 3000 PO Box 500, East Melbourne Vic 3002 Telephone: +61-3-8636 2325 Telefax: +61-3-8636 2813 -- View this message in context: http://osgeo-org.1560.n6.nabble.com/5-seconds-to-render-130-000-points-typical-GeoServer-WMS-performance-tp4995984p4996235.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
