Thanks for the suggestion! I will experiment with G1 garbage collector and some more memory.
On Sun, Feb 2, 2020 at 3:28 PM Jody Garnett <[email protected]> wrote: > You may wish to consider the G1 garbage collector which uses several > threads to cleanup and provides more consistent overhead (less stop the > world moments, but more cpu use). It works well when using more memory like > 4GB. Indeed I think they are making it the default for java now. > > On Sun, Feb 2, 2020 at 6:54 PM Nedim Oren <[email protected]> wrote: > >> We have a Tomcat installation on Windows Server 2016 Datacenter (14 GB >> rem and ) and using the following settings for JVM. >> >> rem ----------- >> set CATALINA_OPTS=-Djava.awt.headless=true -Dfile.encoding=UTF-8 -server >> -Xmx1536m -Xms256m -XX:MaxPermSize=256m -Xrs >> -XX:SoftRefLRUPolicyMSPerMB=36000 -XX:PerfDataSamplingInterval=500 >> -XX:+UseParallelGC >> rem ----------- >> >> We are new to the GeoServer and Java. >> >> On Sun, Feb 2, 2020 at 6:23 AM Jody Garnett <[email protected]> >> wrote: >> >>> >>> Did you apply the JVM startup options froM the user guide? They are >>> explicitly provided to keep objects in memory longer than is usually for a >>> java program. You could try increasing the time limit and see what happens. >>> >>> In geotools we take charge of the spatial reference system objects to >>> more explicitly manage them in a cache. I am not sure if we take the same >>> steps for the resource pool (which is caching some of the details needed >>> for GetCapabilities). >>> >>> On Tue, Jan 28, 2020 at 7:59 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 >>>> >>> -- >>> -- >>> Jody Garnett >>> >> -- > -- > Jody Garnett >
_______________________________________________ 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
