Open deegree-ci opened 5 years ago
We are seeking community feedback on which approach the performance tuning should be focused:
Base for measurements is the execution time of WMS GetMap request. Resource consumption of CPU and memory has not to be optimized.
We've got funding for a first analysis and improvement of deegree's WMS performance. Users are kindly ask to provide configurations and examples.
With deegree 3.4.20 new options have been added to the deegree CLI aka GML tools (see PR #1229 and updated documentation in https://download.deegree.org/documentation/current/html/#deegree-gml-tools). Using the option referenceData
can highly reduce the complexity of an deegree SQLFeatureStore configuration and thus results in better performance of deegree WMS using this feature store.
WMS performance when using SQLFeatureStore based on complex GML application schema requires improvements. Taken from feedback https://github.com/deegree/deegree3/wiki/UserMeeting_20190314_FOSSGIS (authored by @tfr42).