Re: [Geoserver-users] Inconsistent Response Time for WMS GetCapabilites request!

There are a wide range of tools, perhaps start with this which was included in Java 8. -- Jody Garnett On Sun, 2 Feb 2020 at 21:30, Nedim Oren wrote: > Is there a tool that I can use to get a a profiling session output? > Haven't done this before. > S

Re: [Geoserver-users] Inconsistent Response Time for WMS GetCapabilites request!

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 wrote: > You may wish to consider the G1 garbage collector which uses several > threads to cleanup and provides more consistent overhead (less stop the > worl

Re: [Geoserver-users] Inconsistent Response Time for WMS GetCapabilites request!

Is there a tool that I can use to get a a profiling session output? Haven't done this before. System I am testing is Windows Server 2016 + Java 8 + GeoServer Version 2.16.2 + Apache Tomcat *When the server restarts the first GetCapabilities response is always over a minutes (can go up to 4 minutes

Re: [Geoserver-users] Inconsistent Response Time for WMS GetCapabilites request!

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, 2

Re: [Geoserver-users] Inconsistent Response Time for WMS GetCapabilites request!

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:Per

Re: [Geoserver-users] Inconsistent Response Time for WMS GetCapabilites request!

Just to confirm, there is no such a thing as a "capabilities" object, the capability document is written using a streaming xml API, meaning, it is pushed out bit by bit without building a full in memory representation of it. There is no caching either. What you are seeing might be GC (do you have a

Re: [Geoserver-users] Inconsistent Response Time for WMS GetCapabilites request!

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 exp

Re: [Geoserver-users] Inconsistent Response Time for WMS GetCapabilites request!

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

Re: [Geoserver-users] Inconsistent Response Time for WMS GetCapabilites request!

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 ja...@newmoyergeospatial.com On Tue, Jan 28, 2020 at 1:57 PM Nedim Oren wrote: > Is t

[Geoserver-users] Inconsistent Response Time for WMS GetCapabilites request!

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 g