This document provides information on typical command-line options and environment variables that can affect the performance characteristics of the Java HotSpot Virtual Machine. Unless otherwise noted, all information in this document pertains to both the Java HotSpot Client VM and the Java HotSpot Server VM.
Users of JDKs older than 1.3.0 who wish to port to a Java HotSpot VM, should see Java HotSpot Equivalents of Exact VM flags.
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:
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.
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.)
|
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 this tuning 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:+StringCache |
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.
|
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 -histo command provides equivalent functionality.
|
-XX:-PrintConcurrentLocks |
Print java.util.concurrent locks in Ctrl-Break thread dump. Manageable. (Introduced in 6.) The jstack -l command 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.
|
<!-- =================== --><!-- END OF MAIN CONTENT --><!-- =================== --><!--stopindex--><!-- BEGIN D7 COMPONENT V.5 --><!--EndFragment-->
相关推荐
### Sun JVM原理与内存管理 #### 一、Sun JDK 1.6 GC (Garbage Collector) Sun JDK 1.6 的垃圾收集器(GC)是其内存管理的关键组成部分,它负责自动地回收不再使用的对象所占用的内存。本文将详细介绍Sun JDK 1.6 GC...
JVM参数设置是优化Java应用性能的关键环节,它可以帮助我们控制JVM的行为,如内存分配、垃圾回收策略、线程调度等。下面将详细介绍一些重要的JVM参数及其作用。 1. 内存设置: - `-Xms` 和 `-Xmx`:这两个参数用于...
常用jvm参数都在这张图中,参考起来方便,是国外大神整理的
JVM内存回收最全的手册书籍,详细介绍了各种内存回收算法,是Java程序员进阶的必备书籍
### Tomcat 6.0 修改启动内存设置及 Java JVM 参数配置详解 #### 一、背景与目的 在部署和运行 Java Web 应用时,合理地配置应用服务器(如 Apache Tomcat)的内存是非常重要的。这不仅可以提升应用程序的性能,还...
sunJVM的源代码
### 关键业务系统JVM参数推荐 #### 一、引言 在关键业务系统中,除了追求高吞吐量和低延迟之外,系统的稳定性和问题排查的便捷性同样至关重要。因此,选择合适的JVM参数变得尤为重要。本文将详细介绍一些常用的JVM...
sunJVM的源代码8
### IBM JVM 参数选项详解 IBM Java虚拟机(JVM)为开发者提供了丰富的配置选项来优化应用程序性能、诊断问题以及调整各种资源使用情况。本文将详细解释IBM JVM中的关键参数及其功能,帮助您更好地管理和调优Java...
sunJVM的源代码9
### 设置Eclipse的JVM参数 #### 一、引言 在进行Java开发时,Eclipse作为一款广泛使用的集成开发环境(IDE),其性能优化对于提高开发效率和应用稳定性至关重要。其中,设置合适的JVM(Java虚拟机)参数是优化...
Java虚拟机(JVM)是Java程序运行的基础,它的配置参数和垃圾收集(GC)机制对于优化应用程序性能至关重要。本文将深入探讨JVM参数及其与Java垃圾收集相关的知识。 一、JVM参数详解 JVM参数可以分为三类:启动参数...
### JVM参数设置详解 在Java应用开发与维护过程中,JVM(Java虚拟机)的配置至关重要,它直接影响到应用程序的性能表现与稳定性。本文将基于提供的文件内容,深入解析Linux环境下JVM的基本参数设置方法及原理。 ##...
### JVM参数配置详解 #### 一、理解JVM参数配置的重要性 Java Virtual Machine (JVM) 是运行Java程序的核心环境,其性能优化很大程度上依赖于正确的JVM参数配置。合理配置JVM参数不仅可以显著提升应用程序的运行...
本篇文件内容主要介绍了JVM优化的第三部分,重点围绕Tomcat参数调优、JVM参数调优、JVM字节码优化以及代码优化等几个方面。下面是针对这些知识点的详细解释: 1. Tomcat参数调优 在Tomcat参数调优部分,首先介绍了...
JVM 参数与系统性能的优化 在 Java 虚拟机(JVM)中,参数设置对系统性能的影响是至关重要的。通过设置合适的 JVM 参数,可以提高系统性能,减少垃圾回收的频率和时间,提高应用程序的执行效率。 第一点:设置堆栈...
【JVM参数配置详解】 Java Virtual Machine (JVM) 是Java程序的核心组成部分,它负责解析和执行Java程序的字节码。JVM的设计目标是提供跨平台的运行环境,通过在实际硬件上模拟一个虚拟的计算机系统,使得Java程序...
Linux 服务器调优与 JVM 参数调优 本文主要介绍了 Linux 服务器调优和 JVM 参数调优的相关知识点,以便提高服务器性能和 JVM 应用程序的运行效率。 Linux 服务器调优 Linux 服务器调优是指对 Linux 操作系统的...
JVM参数调优是优化Java应用程序性能的关键环节,尤其是在服务器端的应用中,如Web服务器Resin。本实践案例中,作者分别尝试了三种不同的垃圾回收(GC)策略:串行回收、并行回收和并发回收,并针对每种策略提供了...