I have read the aticle about jvm and system tuning (https://apacheignite.readme.io/docs/jvm-and-system-tuning#section-detailed-garbage-collection-stats).
Below are sets of advanced JVM configurations for applications that might generate high numbers of temporary objects hence triggering long pauses due to garbage collection activities. -server -Xms8g -Xmx8g -XX:+UseParNewGC -XX:+UseConcMarkSweepGC -XX:+UseTLAB -XX:NewSize=128m -XX:MaxNewSize=128m -XX:MaxTenuringThreshold=0 -XX:SurvivorRatio=1024 -XX:+UseCMSInitiatingOccupancyOnly -XX:CMSInitiatingOccupancyFraction=40 -XX:MaxGCPauseMillis=1000 -XX:InitiatingHeapOccupancyPercent=50 -XX:+UseCompressedOops -XX:ParallelGCThreads=8 -XX:ConcGCThreads=8 -XX:+DisableExplicitGC I noticed it recommend to "DisableExplicitGC". I thought it is appropriate for the Ignite server. But if I run Ignite by client mode for Continuous query or Data Streamers, must this parameter "DisableExplicitGC" also be like that? -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Question-about-DisableExplicitGC-tp7682.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.
