GML responses forces the full vector catalog to be loaded (and eventually
re-disposed of)
-----------------------------------------------------------------------------------------
Key: GEOS-3653
URL: http://jira.codehaus.org/browse/GEOS-3653
Project: GeoServer
Issue Type: Bug
Reporter: Andrea Aime
Assignee: Justin Deoliveira
Priority: Critical
Fix For: 2.0.1
When doing any request that requires GML encoding all of the feature types are
extracted from the catalog to feed the xml configuration. If the catalog is big
that is going to be a serious performance problem, as the ResourcePool keeps
only a limited amount of feature types in cache, and recomputing each feature
type from the datastore might involve a number of queries against the backed
(especially true with database backed stores).
This prevents GS WFS from scaling up the number of layers that can be handled.
This could be addressed in a number of ways (not necessarily exclusive with
each other):
- by making the GetFeature just pass in the feature type it needs instead of
them all
- by allowing the admin to tune the ResourcePool cache size
- by using soft references maps in the catalog (would work for feature types,
they don't really need any active disposing, no?)
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now. http://p.sf.net/sfu/bobj-july
_______________________________________________
Geoserver-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geoserver-devel
