Here's the flags we're using: -Xms3G -Xmx3G -XX:MaxPermSize=100M -Xloggc:gc-%ID%.log -XX:+PrintGCDateStamps -XX:+PrintGCDetails -XX:+PrintTenuringDistribution -XX:+PrintGCApplicationStoppedTime -XX:+DisableExplicitGC -XX:+UseGCLogFileRotation -XX:NumberOfGCLogFiles=10 -XX:GCLogFileSize=50M -XX:+UseCompressedOops -XX:+AlwaysPreTouch -XX:+UseG1GC -XX:MaxGCPauseMillis=20 -XX:+HeapDumpOnOutOfMemoryError -XX:HeapDumpPath=OOMDump-%ID%.log
Here's a link to a GC log analysis (takes several minutes to load) http://gceasy.io/my-gc-report?p=L2hvbWUvcmFtL3VwbG9hZC9pbnN0YW5jZTEvc2hhcmVkLzIwMTYtNi0zL2djbG9nLnppcC0wLTU3LTE3 This is definitely outside the realm of my knowledge, so don't use this as any kind of benchmark. I'm curious if anyone can comment on any suggested adjustments? I feel like we have a ton of churn in our young gen, but really don't have the experience tuning java's GC or any examples to compare it with. Thanks! On Fri, Jun 3, 2016 at 3:41 PM, Otis Gospodnetić <otis.gospodne...@gmail.com > wrote: > Hi, > > +1 for G1 for large heaps where you are seeing big GC pauses. Works well > for us. > See: > https://sematext.com/blog/2013/06/24/g1-cms-java-garbage-collector/ > > Otis > -- > Monitoring - Log Management - Alerting - Anomaly Detection > Solr & Elasticsearch Consulting Support Training - http://sematext.com/ > > > On Tue, May 31, 2016 at 5:21 AM, Spico Florin <spicoflo...@gmail.com> > wrote: > >> Hello! >> I would like the community the following: >> 1. Are you using the G1 garbage collector for your workers/supervisors >> in production? >> 2. Have you observed any improvement added by adding this GC style? >> 3. What are the JVM options that you are using and are a good fit for you? >> >> Thank you in advance. >> Regards, >> Florin >> >> >
