JaCoLine - Viewing Historical Command Line #8140

Analysis Date JDK Operating System CPU Architecture Debug JVM?
2023-05-26 OpenJDK12 Linux x86 N
Results
Switches Identified
Switch Analysis
Name Type Description Default Value Your Value
ms <size> set initial Java heap size 256m
Analysis OK
Name Type Description Default Value Your Value
mx <size> set maximum Java heap size 1024m
Analysis OK
Name Type Description Default Value Your Value
ss <size> set java thread stack size 512k
Analysis OK
Name Type Description Default Value Your Value
CompressedClassSpaceSize size_t Maximum size of class area in Metaspace when compressed
class pointers are used
1*G in range(1*M, 3*G) 64m
Analysis OK
Name Type Description Default Value Your Value
MaxMetaspaceSize size_t Maximum size of Metaspaces (in bytes) max_uintx 256m
Analysis OK
Name Type Description Default Value Your Value
UseShenandoahGC boolean Use the Shenandoah garbage collector false true
Analysis OK
Name Type Description Default Value Your Value
UnlockExperimentalVMOptions boolean Enable normal processing of flags relating to experimental
features
false true
Analysis OK
Name Type Description Default Value Your Value
ShenandoahUncommit boolean Allow Shenandoah to uncommit unused memory. true true
Analysis OK
Name Type Description Default Value Your Value
ShenandoahUncommitDelay int Shenandoah would start to uncommit memory for regions that were
not used for more than this time. First use after that would
incur allocation stalls. Actively used regions would never be
uncommitted, because they never decay. Time is in milliseconds.
Setting this delay to 0 effectively makes Shenandoah to
uncommit the regions almost immediately.
5*60*1000 30000
Analysis OK
Name Type Description Default Value Your Value
ShenandoahGCHeuristics string The heuristics to use in Shenandoah GC. Possible values:
*) adaptive - adapt to maintain the given amount of free heap;
*) static - start concurrent GC when static free heap
threshold and static allocation threshold are
tripped;
*) passive - do not start concurrent GC, wait for Full GC;
*) aggressive - run concurrent GC continuously, evacuate
everything;
*) compact - run GC with lower footprint target, may end up
doing continuous GC, evacuate lots of live
objects, uncommit heap aggressively;
adaptive compact
Analysis OK