Documentation Contents

JRockit Command Flags Migrated to HotSpot

The following Java command flags have been ported from the Oracle JRockit VM and are now available in the HotSpot VM in JDK7 Update 4.

Comparison of Flags in HotSpot and JRockit

Jrockit HotSpot Definition
-Xlargepages -XX:+UseLargePages Use this flag to enable large page support. Large pages are enabled by default on Solaris.
-Xlargepages:exitOnFailure=true (no equivalent) In JRockit, if this flag is set to true, the JVM exits if a large page request fails. HotSpot doesn't have an equivalent flag. If a large page request fails at JVM initialization, the HotSpot JVM prints a error message. However, execution continues using the default page size.
-XX:MaxLargePageSize=N -XXLargePageSizeInBytes=N Sets the large page size in bytes.
-XX:+UseLargePagesForHeap default behavior for HotSpot If large pages are enabled in HotSpot, then they will always be used for the Java heap.
-Xms -Xms Sets the initial heap size
-Xmx -Xmx Sets the maximum heap size. For server deployments, -Xms and -Xms are often set to the same value
-Xns -Xmn or -XX:NewSize Sets the size of the young generation (nursery).
-XXaggressive -XX:+AggressiveOpts Enables aggressive optimization. The type and level of optimization varies between Jrockit and HotSpot, and between releases. Therefore it is not directly comparable between JVMs.
-Xgc:genpar -XX:+UseParallelOldGC Enables the parallel garbage collectors that are optimized for throughput and average response time.
-Xpausetarget -XX:MaxGCPauseMillis=nnn Sets a target for the maximum GC pause time. This is a soft goal, and the JVMs will both do their best effort to achieve it. In Jrockit, the default value is 500ms. In HotSpot, there is no maximum value set by default.
-XgcPrio:pausetime -XX:+UseConcMarkSweepGC or -XX:+UseG1GC In HotSpot, these flags enables either the Concurrent Mark Sweep (CMS) or the G1 garbage collectors.
-Xxgcthreads=n -XX:ParallelGCThreads=n Sets the number of GC threads in the parallel collectors.
-Xverbose:opt -XX:+PrintCompilation Prints verbose output from the HotSpot dynamic runtime compilers.
-Xverbose:gcpause -XX:+PrintGCDetails -XX:+PrintGCTimeStamps Prints garbage collection output along with time stamps.
-xverbose:compaction -XX:+PrintGCDetails -XX:+PrintGCTimeStamps Prints garbage collection output along with time stamps.
-XxcompressedRefs -XX:+UseCompressedOops (default) Enables compressed references in 64-bit JVMs. NOTE: Need to cross reference with HotSpot VM tuning options doc.
-XX:+UseCallProfiling default behavior in HotSpot In JRockit, this flag enables call profiling for use in JIT optimization. This is the default behavior in HotSpot.
-XX:+UseAllocPrefetch -XX:AllocationPrefetchStyle=2 (default) Sets the style of prefetch used during allocation.
-XX:tlasize:min=4k,preferred=2048k -XX:TLABSize=n This flag tunes the size of TLABs. Both Jrockit and HotSpot use TLABS by default, and HotSpot automatically sizes TLABs based on allocation patterns.
Jrockit is more aggressive processing soft references by default -XX:SoftRefLRUPolicyMSPerMB=0 This flag enabled aggressive processing of software references. Use this flag if HotSpot GC is impacted by software reference count.
Jrockit internal data structures are tuned for high class count by default. -XX:+UnlockExperimentalVMOptions -XX:PredictedClassLoadCount=n Use this flag if your application loads a lot of classes, and especially if class.forName() is used heavily. The recommended value is the number of classes loaded as shown in the output from -verbose:class.

Oracle and/or its affiliates Copyright © 1993, 2015, Oracle and/or its affiliates. All rights reserved.
Contact Us