JaCoLine - Viewing Historical Command Line #6244

Analysis Date JDK Operating System CPU Architecture Debug JVM?
2022-11-24 OpenJDK17 Windows - Any - Y
Results
Switches Identified
Switch Analysis
Name Type Description Default Value Your Value
mx <size> set maximum Java heap size 4G
Analysis OK
Name Type Description Default Value Your Value
ms <size> set initial Java heap size 4G
Analysis OK
Name Type Description Default Value Your Value
EnableJVMCI boolean Enable JVMCI false true
Analysis OK
Name Type Description Default Value Your Value
UseJVMCICompiler boolean Use JVMCI as the default compiler. Defaults to true if
EnableJVMCIProduct is true.
false true
Analysis OK
Name Type Description Default Value Your Value
EagerJVMCI boolean Force eager JVMCI initialization false true
Analysis OK
Name Type Description Default Value Your Value
AlwaysPreTouch boolean Force all freshly committed pages to be pre-touched false true
Analysis OK
Name Type Description Default Value Your Value
PerfDisableSharedMem boolean Store performance data in standard memory false true
Analysis OK
Name Type Description Default Value Your Value
UsePerfData boolean Flag to disable jvmstat instrumentation for performance testing
and problem isolation purposes
true false
Analysis OK
Name Type Description Default Value Your Value
AggressiveHeap boolean Optimize heap options for long-running memory intensive apps false true
Analysis OK
Name Type Description Default Value Your Value
UseLargePages boolean Use large page memory false true
Analysis OK
Name Type Description Default Value Your Value
LargePageSizeInBytes size_t Maximum large page size used (0 will use the default large
page size for the environment as the maximum)
0 in range(0, max_uintx) 2M
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
ShenandoahGuaranteedGCInterval int Many heuristics would guarantee a concurrent GC cycle at
least with this interval. This is useful when large idle
intervals are present, where GC can run without stealing
time from active application. Time is in milliseconds.
Setting this to 0 disables the feature.
5*60*1000 1000000
Analysis OK
Name Type Description Default Value Your Value
DisableExplicitGC boolean Ignore calls to System.gc() false true
Analysis OK
Name Type Description Default Value Your Value
NmethodSweepActivity int Removes cold nmethods from code cache if > 0. Higher values
result in more aggressive sweeping
10 in range(0, 2000) 1
Analysis OK
Name Type Description Default Value Your Value
ReservedCodeCacheSize int Reserved code cache size (in bytes) - maximum code cache size
CPUDefault
aarch6432*M
arm32*M
ppc32*M
riscv48*M
s39048*M
x8632*M
400M
Analysis OK
Name Type Description Default Value Your Value
NonNMethodCodeHeapSize int Size of code heap with non-nmethods (in bytes)
CPUDefault
aarch645*M
arm5*M
ppc5*M
riscv5*M
s3905*M
x865*M
12M
Analysis OK
Name Type Description Default Value Your Value
ProfiledCodeHeapSize int Size of code heap with profiled methods (in bytes)
CPUDefault
aarch6414*M
arm14*M
ppc14*M
riscv22*M
s39022*M
x8614*M
194M
Analysis OK
Name Type Description Default Value Your Value
NonProfiledCodeHeapSize int Size of code heap with non-profiled methods (in bytes)
CPUDefault
aarch6413*M
arm13*M
ppc13*M
riscv21*M
s39021*M
x8613*M
194M
Analysis OK
Name Type Description Default Value Your Value
DontCompileHugeMethods boolean Do not compile methods > HugeMethodLimit true false
Analysis OK
Name Type Description Default Value Your Value
MaxNodeLimit int Maximum number of nodes 80000 in range(1000, max_jint / 3) 240000
Analysis OK
Name Type Description Default Value Your Value
NodeLimitFudgeFactor int Fudge Factor for certain optimizations 2000 8000
Analysis OK
Name Type Description Default Value Your Value
UseVectorCmov boolean Use Vectorized Cmov false true
Analysis OK
Name Type Description Default Value Your Value
UseFastUnorderedTimeStamps boolean Use platform unstable time where supported for timestamps only false true
Analysis OK
Name Type Description Default Value Your Value
UseCriticalJavaThreadPriority boolean Java thread priority 10 maps to critical scheduling priority false true
Analysis OK
Name Type Description Default Value Your Value
ThreadPriorityPolicy int 0 : Normal.
VM chooses priorities that are appropriate for normal
applications.
On Windows applications are allowed to use higher native
priorities. However, with ThreadPriorityPolicy=0, VM will
not use the highest possible native priority,
THREAD_PRIORITY_TIME_CRITICAL, as it may interfere with
system threads. On Linux thread priorities are ignored
because the OS does not support static priority in
SCHED_OTHER scheduling class which is the only choice for
non-root, non-realtime applications.

1 : Aggressive.
Java thread priorities map over to the entire range of
native thread priorities. Higher Java thread priorities map
to higher native thread priorities. This policy should be
used with care, as sometimes it can cause performance
degradation in the application and/or the entire system. On
Linux/BSD/macOS this policy requires root privilege or an
extended capability.
0 in range(0, 1) 1
Analysis OK