Other Java Virtual Machine arguments
These Java™ Virtual Machine (JVM) arguments were identified as beneficial to the workload used here, and other benchmarks with similar characteristics to the workload. The values are specific to the workload and should not be expected to necessarily benefit other workloads or production environments.
-noclassgc -Xss128k -Xgcpolicy:gencon -Xmo768m -Xcodecache16m -Xgcthreads4
-Djava.net.preferIPv4Stack=true -Dsun.net.inetaddr.ttl=0- -Xgcpolicy:gencon
- Directs the JVM to manage its heap using the generational concurrent or split heap. This benefits applications with many short-lived objects, and is discussed in System setup.
- -Xmo768m
- Specifies that 768 MB of memory is to be dedicated to the tenured part of the split heap, with the remaining part of the JVM heap dedicated to buffers and new object or nursery areas. This value is changed for some 64-bit measurements.
- -Xnoclassgc
- Directs the JVM to not perform garbage collection on the classes
that reside in the permanent or tenured space in the split heap.
Unloading of these classes means that future references require a costly load from the file system, instead of an efficient memory load. This is a commonly used setting for workloads with repetitive use of the same classes.
- -Xgcthreads4
- Instructs the JVM to start four threads for garbage collection. The default value is to have as many garbage collection threads as there are available processors.
- -Xss128k
- Allocates 128 KB of memory for the native stack area of each thread. The native stack area is used for native library loads by Java from the C/C++ environment, which is the native layer.
- -Xcodecache16m
- Sets the size of each block of memory that is allocated to store native code of compiled Java methods to 16 MB. By default, this size is selected internally according to the CPU architecture and the capacity of your system.