+ user mailing list - developer mailing list This question would be better addressed to the user mailing list.
There are a number of causes of "long JVM pauses,” so it’s difficult to be prescriptive. I’d start by logging more information about Java’s garbage collection. More information in the documentation here: https://ignite.apache.org/docs/latest/perf-and-troubleshooting/memory-tuning#generic-gc-settings Given the data provided, I’d say your heap space is likely excessive. Having more heap space isn’t necessarily better. Regards, Stephen > On 7 Mar 2024, at 14:54, Kalwakuntla, Srinivas > <srinivas.kalwakun...@accenture.com.INVALID> wrote: > > Dear Ignite Team, > > Hope this email finds your well ! > > Reaching out to you, as currently we are facing performance issue with Apache > Ignite. Our application is running on Azure Kubernetes (v1.27.1), which has > 24 nodes of size "Standard_F64s_v2" (handling roughly 13million of records). > Frequently we are getting "[WARNING][jvm-pause-detector-worker][IgniteKernal] > Possible too long JVM pause: xxxx milliseconds", while performing any > operations such as reading, encoding etc. > > Here below is the system information: > > System Information (Apache Ignite Clusters) > Heap size: 32GB out of 64GB of memory > CPUs: Standard_F64s_v2 > The number of server instances: 24 > IOWait: within normal range > IOPS: 10k-600K per hr > JDK: Oracle JDK8, 1.8.0_281 > APACHE IGNITE - 2.14.0 > > GC configuration in ignite.sh: > > XX:-UseContainerSupport > -XX:+AlwaysPreTouch > -XX:+UseG1GC > -XX:+ScavengeBeforeFullGC > -XX:+DisableExplicitGC" > > Please assist us in identifying the underlying source of this problem. > Thank you, > Srinivas >
