Our team deploys GeoServers fronting datasets regularly upwards of a
hundred million (occasionally billions) records. All our datasets are time
enabled which often causes issues for the responsiveness of our WMS
GetCapabilities. Everything goes fairly well as long as the aggregates
performed can take advantage of temporal indices (we use Postgres
primarily), but often new developers will create data missing indices or
with poorly performing joins. This affects all layer consumption, as we
heavily rely on GetCapabilities to self discover the available datasets in
our applications.
I saw a mailing list post from quite awhile back that also brought this
issue up:
http://osgeo-org.1560.x6.nabble.com/WMS-request-getcapabilities-takes-a-loooooooooooooong-time-to-return-td5003095.html
Has there been any thought for a GeoServer native solution for this?
Something as simple as a global setting that would allow caching
GetCapabilities with a configurable TTL would be tremendously helpful.
How are others solving this problem? Fronting GeoServer with a web cache
(Varnish or the like) to cache GetCapabilities requests that way? Never
enabling time dimension on layers when this is a problem?
Thanks,
Jonathan Meyer
Sr. Software Engineer
Applied Information Sciences
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Geoserver-users mailing list
Please make sure you read the following two resources before posting to this
list:
- Earning your support instead of buying it, but Ian Turton:
http://www.ianturton.com/talks/foss4g.html#/
- The GeoServer user list posting guidelines:
http://geoserver.org/comm/userlist-guidelines.html
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users
