问题
Currently, we are using the incremental garbage collector by adding -Xincgc to the java command. In JDK 8 this switch is deprecated. So what's the equivalent replacement for it? -XX:+UseG1GC?
Background: The application has a heap of 8GB and creates a lot of short living objects. I noticed that it often paused for some seconds to do garbage collection. Out of curiosity I added the -Xincgc and found that the pauses were gone and overall performance improved ~4 times.
Unfortunately, I did not find any information about what type of garbage collector the -Xincgc triggers. There's the CMS (Concurrent mark and sweep) and the new G1 (Garbage first). But what do I get with -Xincgc?
回答1:
For Oracle/OpenJDK 8 the default collector on most machines is the Parallel Throughput Collector, except for some 32bit windows machines where it can be the Serial GC.
Xincgc is CMS in incremental mode. The main benefit you're seeing probably is caused by switching from the Throughput Collector to CMS, not from the incremental mode, which is designed for single-core CPUs.
Incremental Mode is also deprecated, so simply enable CMS via -XX:+UseConcMarkSweepGC and see if that works for you.
Of course you can also try G1GC, which is also designed to reach low pause time goals and has the advantage that it does not suffer from fragmentation like CMS does and thus is less likely to experience concurrent mode failures which result in a single-threaded stop the world collection.
So, try both and measure.
See also: Oracle's Java 8 GC Tuning Guides
回答2:
Until this option completely deprecated by Oracle in the newer version. We could still use this, by applying the following jvm params:
-XX:+UseConcMarkSweepGC -XX:+CMSIncrementalMode -XX:+PrintGCDetails -XX:+PrintGCTimeStamps
The later 2 params are for logging on GC activities.
来源：https://stackoverflow.com/questions/33919213/is-xxuseg1gc-the-correct-replacement-for-xincgc