GC configuration at Ztesoft Vietnam site
nohup $JAVA_BIN/java -Xms2048M -Xmx2048M -Xmn768M -XX:ParallelGCThreads=20 -XX:+UseConcMarkSweepGC -XX:+UseParNewGC -XX:CMSFullGCsBeforeCompaction=5 -XX:+UseCMSCompactAtFullCollection -DZSMART_HOME=$ZSMART_HOME -Dz_app=$APP_NAME -cp $CLASSPATH $MAIN_CLASS &
--------------
The startup script young geneartion of Qbao enterprise app accounts for 50%
export JAVA_OPTS="-server -d64 -Djava.awt.headless=true -Xms8196m -Xmx8196m -Xmn4000m -XX:Perm Size=64m -XX:MaxPermSize=256m -XX:+UseConcMarkSweepGC -XX:+UseCMSCompactAtFullCollection -XX:CMSMaxAbortablePrecleanTime=5000 -XX:CMSInitiatingOccupancyFraction=80 -XX:+DisableExplicitGC -XX:+CMS ClassUnloadingEnabled -XX:CMSFullGCsBeforeCompaction=10 -Djava.net.preferIPv4Stack=true -Djava.util .Arrays.useLegacyMergeSort=true
The startup script of Qbao enterprise app, young generation 8G, accounts for 60%+, minorGc takes longer, throughput rate does not improve, it does not help performance, and the effect is not as good as 4G young generation
-Xms12000m -Xmx12000m -Xmn8000m
-------------------------------------------
From the report seen by Tingyun, the actual space allocation of the JVM and the JVM parameter configuration in the startup script are exactly the same
requires attention:
Permanent space, code cache belong to non-heap memory, survivor space has two
