Categories of Java HotSpot VM Options
Standard options recognized by the Java HotSpot VM are described on the Java Application Launcher reference pages for Windows, Solaris and Linux. This document deals exclusively with non-standard options recognized by the Java HotSpot VM:
- Options that begin with
-X
are non-standard (not guaranteed to be supported on all VM implementations), and are subject to change without notice in subsequent releases of the JDK.
- Options that are specified with
-XX
are not stable and are not recommended for casual use. These options are subject to change without notice.
Some Useful -XX Options
Default values are listed for Java SE 6 for Solaris Sparc with -server. Some options may vary per architecture/OS/JVM version. Platforms with a differing default value are listed in the description.
- Boolean options are turned on with
-XX:+<option>
and turned off with -XX:-<option>
.
- Numeric options are set with
-XX:<option>=<number>
. Numbers can include 'm' or 'M' for megabytes, 'k' or 'K' for kilobytes, and 'g' or 'G' for gigabytes (for example, 32k is the same as 32768).
- String options are set with
-XX:<option>=<string>
, are usually used to specify a file, a path, or a list of commands
Flags marked as manageable are dynamically writeable through the JDK management interface (com.sun.management.HotSpotDiagnosticMXBean API) and also through JConsole. In Monitoring and Managing Java SE 6 Platform Applications, Figure 3 shows an example. The manageable flags can also be set through jinfo -flag.
The options below are loosely grouped into three categories.
Behavioral Options
Option and Default Value
Description
-XX:-AllowUserSignalHandlers |
Do not complain if the application installs signal handlers. (Relevant to Solaris and Linux only.) |
-XX:AltStackSize=16384 |
Alternate signal stack size (in Kbytes). (Relevant to Solaris only, removed from 5.0.) |
-XX:-DisableExplicitGC |
Disable calls to System.gc(), JVM still performs garbage collection when necessary. |
-XX:+FailOverToOldVerifier |
Fail over to old verifier when the new type checker fails. (Introduced in 6.) |
-XX:+HandlePromotionFailure |
The youngest generation collection does not require a guarantee of full promotion of all live objects. (Introduced in 1.4.2 update 11) [5.0 and earlier: false.] |
-XX:+MaxFDLimit |
Bump the number of file descriptors to max. (Relevant to Solaris only.) |
-XX:PreBlockSpin=10 |
Spin count variable for use with -XX:+UseSpinning. Controls the maximum spin iterations allowed before entering operating system thread synchronization code. (Introduced in 1.4.2.) |
-XX:-RelaxAccessControlCheck |
Relax the access control checks in the verifier. (Introduced in 6.) |
-XX:+ScavengeBeforeFullGC |
Do young generation GC prior to a full GC. (Introduced in 1.4.1.) |
-XX:+UseAltSigs |
Use alternate signals instead of SIGUSR1 and SIGUSR2 for VM internal signals. (Introduced in 1.3.1 update 9, 1.4.1. Relevant to Solaris only.) |
-XX:+UseBoundThreads |
Bind user level threads to kernel threads. (Relevant to Solaris only.) |
-XX:-UseConcMarkSweepGC |
Use concurrent mark-sweep collection for the old generation. (Introduced in 1.4.1) |
-XX:+UseGCOverheadLimit |
Use a policy that limits the proportion of the VM's time that is spent in GC before an OutOfMemory error is thrown. (Introduced in 6.) |
-XX:+UseLWPSynchronization |
Use LWP-based instead of thread based synchronization. (Introduced in 1.4.0. Relevant to Solaris only.) |
-XX:-UseParallelGC |
Use parallel garbage collection for scavenges. (Introduced in 1.4.1) |
-XX:-UseParallelOldGC |
Use parallel garbage collection for the full collections. Enabling this option automatically sets -XX:+UseParallelGC. (Introduced in 5.0 update 6.) |
-XX:-UseSerialGC |
Use serial garbage collection. (Introduced in 5.0.) |
-XX:-UseSpinning |
Enable naive spinning on Java monitor before entering operating system thread synchronizaton code. (Relevant to 1.4.2 and 5.0 only.) [1.4.2, multi-processor Windows platforms: true] |
-XX:+UseTLAB |
Use thread-local object allocation (Introduced in 1.4.0, known as UseTLE prior to that.) [1.4.2 and earlier, x86 or with -client: false] |
-XX:+UseSplitVerifier |
Use the new type checker with StackMapTable attributes. (Introduced in 5.0.)[5.0: false] |
-XX:+UseThreadPriorities |
Use native thread priorities. |
-XX:+UseVMInterruptibleIO |
Thread interrupt before or with EINTR for I/O operations results in OS_INTRPT. (Introduced in 6. Relevant to Solaris only.) |
Back to Options
Performance Options
Option and Default Value
Description
-XX:+AggressiveOpts |
Turn on point performance compiler optimizations that are expected to be default in upcoming releases. (Introduced in 5.0 update 6.) |
-XX:CompileThreshold=10000 |
Number of method invocations/branches before compiling [-client: 1,500] |
-XX:LargePageSizeInBytes=4m |
Sets the large page size used for the Java heap. (Introduced in 1.4.0 update 1.) [amd64: 2m.] |
-XX:MaxHeapFreeRatio=70 |
Maximum percentage of heap free after GC to avoid shrinking. |
-XX:MaxNewSize=size |
Maximum size of new generation (in bytes). Since 1.4, MaxNewSize is computed as a function of NewRatio. [1.3.1 Sparc: 32m; 1.3.1 x86: 2.5m.] |
-XX:MaxPermSize=64m |
Size of the Permanent Generation. [5.0 and newer: 64 bit VMs are scaled 30% larger; 1.4 amd64: 96m; 1.3.1 -client: 32m.] |
-XX:MinHeapFreeRatio=40 |
Minimum percentage of heap free after GC to avoid expansion. |
-XX:NewRatio=2 |
Ratio of new/old generation sizes. [Sparc -client: 8; x86 -server: 8; x86 -client: 12.]-client: 4 (1.3) 8 (1.3.1+), x86: 12] |
-XX:NewSize=2.125m |
Default size of new generation (in bytes) [5.0 and newer: 64 bit VMs are scaled 30% larger; x86: 1m; x86, 5.0 and older: 640k] |
-XX:ReservedCodeCacheSize=32m |
Reserved code cache size (in bytes) - maximum code cache size. [Solaris 64-bit, amd64, and -server x86: 48m; in 1.5.0_06 and earlier, Solaris 64-bit and and64: 1024m.] |
-XX:SurvivorRatio=8 |
Ratio of eden/survivor space size [Solaris amd64: 6; Sparc in 1.3.1: 25; other Solaris platforms in 5.0 and earlier: 32] |
-XX:TargetSurvivorRatio=50 |
Desired percentage of survivor space used after scavenge. |
-XX:ThreadStackSize=512 |
Thread Stack Size (in Kbytes). (0 means use default stack size) [Sparc: 512; Solaris x86: 320 (was 256 prior in 5.0 and earlier); Sparc 64 bit: 1024; Linux amd64: 1024 (was 0 in 5.0 and earlier); all others 0.] |
-XX:+UseBiasedLocking |
Enable biased locking. For more details, see thistuning example. (Introduced in 5.0 update 6.) [5.0: false] |
-XX:+UseFastAccessorMethods |
Use optimized versions of Get<Primitive>Field. |
-XX:-UseISM |
Use Intimate Shared Memory. [Not accepted for non-Solaris platforms.] For details, see Intimate Shared Memory. |
-XX:+UseLargePages |
Use large page memory. (Introduced in 5.0 update 5.) For details, see Java Support for Large Memory Pages. |
-XX:+UseMPSS |
Use Multiple Page Size Support w/4mb pages for the heap. Do not use with ISM as this replaces the need for ISM. (Introduced in 1.4.0 update 1, Relevant to Solaris 9 and newer.) [1.4.1 and earlier: false] |
-XX:+UseStringCache |
Enables caching of commonly allocated strings. |
-XX:AllocatePrefetchLines=1 |
Number of cache lines to load after the last object allocation using prefetch instructions generated in JIT compiled code. Default values are 1 if the last allocated object was an instance and 3 if it was an array. |
-XX:AllocatePrefetchStyle=1 |
Generated code style for prefetch instructions. 0 - no prefetch instructions are generate*d*, 1 - execute prefetch instructions after each allocation, 2 - use TLAB allocation watermark pointer to gate when prefetch instructions are executed. |
-XX:+UseCompressedStrings |
Use a byte[] for Strings which can be represented as pure ASCII. (Introduced in Java 6 Update 21 Performance Release) |
-XX:+OptimizeStringConcat |
Optimize String concatenation operations where possible. (Introduced in Java 6 Update 20) |
Back to Options
Debugging Options
Option and Default Value
Description
-XX:-CITime |
Prints time spent in JIT Compiler. (Introduced in 1.4.0.) |
-XX:ErrorFile=./hs_err_pid<pid>.log |
If an error occurs, save the error data to this file. (Introduced in 6.) |
-XX:-ExtendedDTraceProbes |
Enable performance-impacting dtrace probes. (Introduced in 6. Relevant to Solaris only.) |
-XX:HeapDumpPath=./java_pid<pid>.hprof |
Path to directory or filename for heap dump.Manageable. (Introduced in 1.4.2 update 12, 5.0 update 7.) |
-XX:-HeapDumpOnOutOfMemoryError |
Dump heap to file when java.lang.OutOfMemoryError is thrown. Manageable. (Introduced in 1.4.2 update 12, 5.0 update 7.) |
-XX:OnError="<cmd args>;<cmd args>" |
Run user-defined commands on fatal error. (Introduced in 1.4.2 update 9.) |
-XX:OnOutOfMemoryError="<cmd args>; <cmd args>" |
Run user-defined commands when an OutOfMemoryError is first thrown. (Introduced in 1.4.2 update 12, 6) |
-XX:-PrintClassHistogram |
Print a histogram of class instances on Ctrl-Break.Manageable. (Introduced in 1.4.2.) The jmap -histocommand provides equivalent functionality. |
-XX:-PrintConcurrentLocks |
Print java.util.concurrent locks in Ctrl-Break thread dump. Manageable. (Introduced in 6.) The jstack -lcommand provides equivalent functionality. |
-XX:-PrintCommandLineFlags |
Print flags that appeared on the command line. (Introduced in 5.0.) |
-XX:-PrintCompilation |
Print message when a method is compiled. |
-XX:-PrintGC |
Print messages at garbage collection. Manageable. |
-XX:-PrintGCDetails |
Print more details at garbage collection. Manageable. (Introduced in 1.4.0.) |
-XX:-PrintGCTimeStamps |
Print timestamps at garbage collection. Manageable(Introduced in 1.4.0.) |
-XX:-PrintTenuringDistribution |
Print tenuring age information. |
-XX:-TraceClassLoading |
Trace loading of classes. |
-XX:-TraceClassLoadingPreorder |
Trace all classes loaded in order referenced (not loaded). (Introduced in 1.4.2.) |
-XX:-TraceClassResolution |
Trace constant pool resolutions. (Introduced in 1.4.2.) |
-XX:-TraceClassUnloading |
Trace unloading of classes. |
-XX:-TraceLoaderConstraints |
Trace recording of loader constraints. (Introduced in 6.) |
-XX:+PerfSaveDataToFile |
Saves jvmstat binary data on exit. |
-XX:ParallelGCThreads= |
Sets the number of garbage collection threads in the young and old parallel garbage collectors. The default value varies with the platform on which the JVM is running. |
-XX:+UseCompressedOops |
Enables the use of compressed pointers (object references represented as 32 bit offsets instead of 64-bit pointers) for optimized 64-bit performance with Java heap sizes less than 32gb. |
-XX:+AlwaysPreTouch |
Pre-touch the Java heap during JVM initialization. Every page of the heap is thus demand-zeroed during initialization rather than incrementally during application execution. |
-XX:AllocatePrefetchDistance= |
Sets the prefetch distance for object allocation. Memory about to be written with the value of new objects is prefetched into cache at this distance (in bytes) beyond the address of the last allocated object. Each Java thread has its own allocation point. The default value varies with the platform on which the JVM is running. |
-XX:InlineSmallCode= |
Inline a previously compiled method only if its generated native code size is less than this. The default value varies with the platform on which the JVM is running. |
-XX:MaxInlineSize=35 |
Maximum bytecode size of a method to be inlined. |
-XX:FreqInlineSize= |
Maximum bytecode size of a frequently executed method to be inlined. The default value varies with the platform on which the JVM is running. |
-XX:LoopUnrollLimit= |
Unroll loop bodies with server compiler intermediate representation node count less than this value. The limit used by the server compiler is a function of this value, not the actual value. The default value varies with the platform on which the JVM is running. |
-XX:InitialTenuringThreshold=7 |
Sets the initial tenuring threshold for use in adaptive GC sizing in the parallel young collector. The tenuring threshold is the number of times an object survives a young collection before being promoted to the old, or tenured, generation. |
-XX:MaxTenuringThreshold= |
Sets the maximum tenuring threshold for use in adaptive GC sizing. The current largest value is 15. The default value is 15 for the parallel collector and is 4 for CMS. |
分享到:
相关推荐
sh 'jdk命令' } } } } ``` 这里,我们使用 `sh` 命令来调用 JDK 命令。我们可以将 JDK 命令写在单引号中,例如 `sh 'javac -version'`。 使用 Maven 或 Gradle 命令 同样,我们也可以使用 Maven 或 Gradle ...
jdk 命令详解 JDK(Java Development Kit)是一套完整的 Java 开发工具包,由 Sun 公司提供,旨在帮助开发者方便地开发和调试 Java 应用程序。JDK 中提供了许多实用的工具和命令,这些命令都位于 JDK 的 bin 目录下...
本文将详细讲解如何在 Jenkinsfile 中调用 JDK 命令工具,并在 Jenkins 容器中进行相应的配置,以实现无需安装完整 JDK 环境即可执行 JDK 相关任务。 1. **容器内放置 JDK 工具包** Jenkins 容器通常是一个轻量级...
JDK 命令学习报告 本文总结了 JDK 中的各种命令,包括 javac、java、javah、jdb 等,详细介绍了 JDB 调试工具的使用方法和命令列表。通过学习这些命令,可以更好地学习和使用 Java 语言。 一、JDK 命令简介 JDK ...
【JDK命令经典讲解全】 在Java开发中,掌握JDK命令是至关重要的,因为它们提供了许多实用的功能,包括编译、运行、调试和管理Java应用程序。本文将深入讲解几个关键的JDK命令,包括`rmic`、`rmid`、`rmiregistry`和...
了解并掌握这些JDK命令,对于日常开发、调试和性能优化都大有裨益。通过阅读《JDK常用命令详解.doc》和《jdk-bin下的命令详解---转载,学习下.txt》,你可以更深入地学习每个命令的用法和具体示例,从而提升你的Java...
【资料分享】JDK的命令详解 rmic 功能说明: rmic 为远程对象生成 stub 和 skeleton。 语法: rmic [ options ] package-qualified-class-name(s) 补充说明: rmic 编译器根据编译后的 Java 类(含有远程...
这些知识点主要围绕着JDK(Java开发工具包)中的基本命令以及如何使用这些命令进行Java程序的编译和运行。 ### 关键知识点 #### 1. JDK简介 - **定义**:JDK是Java Development Kit的缩写,即Java开发工具包。它是...
Java JDK 常用命令详解 Java JDK 提供了多种命令来帮助开发者更好地使用 Java 语言,以下是 JDK 中常用的命令解释: 1. rmic 命令 rmic 命令用于生成 stub 和 skeleton,它可以将 Java 类编译成可供远程对象使用...
在进行开发时,开发者通常会使用集成开发环境(IDE),如IntelliJ IDEA或Eclipse等,它们内部集成了JDK命令,提供了更便利的图形化操作界面。尽管如此,了解JDK命令行工具的使用,对于开发者来说仍然是十分必要的,...
- 接下来,使用`alternatives`命令为每一个需要切换的JDK命令创建链接。例如,对于`javac`命令,可以使用以下命令创建链接: ```bash /usr/sbin/alternatives --install /usr/bin/javac javac /opt/jdk1.6.0_11/...
7. `man`:这里包含了JDK命令的手册页,供用户查询JDK命令的用法。 8. `include`:这个目录包含了C和C++编程语言的头文件,用于开发与Java平台交互的本地代码。 9. `bin`:这个目录包含了Java开发和运行所需的可执行...
"jdk.jcmd"是JDK命令工具,用于诊断和管理Java进程,它包含了很多如jinfo、jmap等命令的实现。 "java.datatransfer"模块处理数据传输,如剪贴板操作和拖放功能。"jdk.internal.vm.compiler",也就是JIT(Just-In-...
2. **测试JDK命令**:在命令提示符中输入`javac -version`或`java -version`,如果显示了JDK版本信息,则说明环境变量配置成功。 #### 四、常见问题及解决方法 - **无法找到或加载主类**:这通常是由于CLASSPATH...
- **man**:包含了JDK命令的手册页。 - **src.zip**:这个文件包含了Java标准库的源代码,可供开发者参考。 2. **环境变量配置**: - **JAVA_HOME**:这个环境变量应设置为JDK的安装目录,例如`C:\Program Files...
- **PATH**:确保`javac`和其他JDK命令能够在任何位置被调用。 - 在系统变量中添加或修改`Path`变量,在其值的最前面加上JDK的bin目录路径: ```plaintext ;C:\Program Files\Java\jdk1.5.0_04\bin; ``` 注意...
6. **man** - 如果存在,将包含有关JDK命令的手册页。 7. **src.zip** - JDK源代码的压缩包,供开发者参考。 总的来说,JDK 1.8.0_221是Java开发和运行的基础,尤其适合服务器环境,其中包含的JRE和jar命令对于...
docker容器中无法使用jdk命令-附件资源
jvm命令行工具,java性能优化,jdk命令工具, jcmd命令、jps命令、jmap命令、jstack命令、jinfo命令、jstat命令