I have recently been building up graphs from WFS data; and have been experiencing some interesting performance characteristics - and I am wondering if they are expected ...
In order to build up a graph ... 1. I request the features in a region using a normal WFS 1.0.0 GetFeatures request. 2. For the first 30 seconds the server performance logs show that GeoServer is using up a full core; and postgis is using a small percentage of another core. During this time no data is being transmitted to the client. 3. At this point the client starts GeoServer starts sending data to the client; GeoServer remains using a full core; and postgis is using a small percentage of another core. I went into the web.xml and confirmed that SPEED was set as the policy ... is this the case of needing to issue the postgis request twice? once to calculate the bounds and again to grab and transmit the data? If so can we avoid this step by assuming the bounds provided during the request "contain" the resulting data? Jody ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ Geoserver-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geoserver-devel
