We don't have any layer with Time Dimension. Some of the Tables are large but I don't think GetCapablities request accesses to the Postgres tables for this request. We already know that this is related to the Java Garbage Collection. After the GetCapabilities Object is created for the first time (when you request first time after restarting the server or after it is disposed by the jave garbage collection process) than if you don't keep requesting GetCapabilities every ~15 minutes than it will be compressed first and then within 2 hrs it will be disposed. After it is disposed it will take 1-3 minutes to re-create the full getCapabilities object. We are trying to use GetCapabilities request as configuration file (passed as a URL parameter) with an map application and unless we set up a scheduled task to request Capabilities every 15 minutes it will suffer form the performance.
On Fri, Jan 31, 2020 at 1:33 PM Jason Newmoyer <[email protected]> wrote: > Interesting. Are you using Time Dimension on any of your layers? Are your > postgres tables large? Are they handling a high volume of inserts/updates? > > Jason Newmoyer > Newmoyer Geospatial Solutions > 843.606.0424 > [email protected] > > > > > On Tue, Jan 28, 2020 at 1:57 PM Nedim Oren <[email protected]> wrote: > >> Is there a way to keep GetCapabilities response time short and consistent? >> >> Response time for WMS GetCapabilites request differs based on the time >> passed between two sequential GetCapabilites requests made to the server. >> For example, if the second request is issued within ~20 minutes of the >> first getCapabilites request than response time for the second request is >> usually around 300-600 ms. >> >> When the time between first and second request increases to 20 min. to 2 >> hours than GetCapabilities response time increases to 12-16 Seconds. If the >> time between first and second request is more than few hours than it takes >> 2 to 5 Minutes to get a GetCapabilities response.I am testing with >> GeoServer Version 2.16.2, have approximately 150 layers, using a Limited >> SRS list (with 3 SRS), all vector data, mostly coming form PostGreSQL >> database and some local shape files. Is there a fix for this problem? >> _______________________________________________ >> 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 >> >> If you want to request a feature or an improvement, also see this: >> https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer >> >> >> [email protected] >> https://lists.sourceforge.net/lists/listinfo/geoserver-users >> >
_______________________________________________ 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 If you want to request a feature or an improvement, also see this: https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer [email protected] https://lists.sourceforge.net/lists/listinfo/geoserver-users
