Listed below are the times for displaying 956,157 points within Geoserver:
Geoserver → PostGIS/PostGres: Initially 88 seconds then each time after (after clearing the client side cache) 40 seconds
Geoserver → Shapefile: Initially 15 seconds then each time after (after clearing the client side cache) 8 seconds
When using Geoserver version 1.6.4 to display 956,157 points it causes Apache Tomcat version 6.0 to be very unstable. Apache Tomcat would stop after 6-10 Geoserver queries against this 956,157 point dataset both when pointing to PostGIS/PostGres and Shapefile.
What could be done to make these queries more stable like configuration to Geoserver, Apache Tomcat or the server that both Geoserver and Apache Tomcat reside on.
What hardware is being used, and in particular, how much memory is allocated for Tomcat's JVM?
When you say "Apache Tomcat would stop" what exactly do you mean? A segfault? A low-level Java exception? Freezing behavior?
---
A. Soroka / Digital Scholarship Services R & D
the University of Virginia Library
On Dec 7, 2008, at 9:21 AM, John Mitchell wrote:
Hi,
Listed below are the times for displaying 956,157 points within Geoserver:
* Geoserver -> PostGIS/PostGres: Initially 88 seconds then each time after (after clearing the client side cache) 40 seconds
* Geoserver -> Shapefile: Initially 15 seconds then each time after (after clearing the client side cache) 8 seconds
When using Geoserver version 1.6.4 to display 956,157 points it causes Apache Tomcat version 6.0 to be very unstable. Apache Tomcat would stop after 6-10 Geoserver queries against this 956,157 point dataset both when pointing to PostGIS/PostGres and Shapefile.
What could be done to make these queries more stable like configuration to Geoserver, Apache Tomcat or the server that both Geoserver and Apache Tomcat reside on.
What hardware is being used, and in particular, how much memory is allocated for Tomcat's JVM?
When you say "Apache Tomcat would stop" what exactly do you mean? A segfault? A low-level Java exception? Freezing behavior?
---
Well ... I Think I face same problem here.
My PostGis have huge records of PoI and Line ... and small number of Polygon.
My CPU is "clasic" P4 and RAM of 2 GB.
I have "Group layer" of PoI, Line, And Polygon.
Single request agains that group will take almost 90% of CPU and more than 90% of RAM, also more than 10 minutes time to render.
What hardware is being used, and in particular, how much memory is allocated for Tomcat's JVM?
When you say "Apache Tomcat would stop" what exactly do you mean? A segfault? A low-level Java exception? Freezing behavior?
---
Well ... I Think I face same problem here.
My PostGis have huge records of PoI and Line ... and small number of Polygon.
My CPU is "clasic" P4 and RAM of 2 GB.
I have "Group layer" of PoI, Line, And Polygon.
Single request agains that group will take almost 90% of CPU and more than 90% of RAM, also more than 10 minutes time to render.
Unfortunately it does not integrate with the GeoTools main renderer at
all, we'd need to redesign the whole thing to allow for pugglable,
context specific renderers.
Cheers
Andrea
--
Andrea Aime
OpenGeo - http://opengeo.org
Expert service straight from the developers.