The general tuning guidelines for java VM.
\nHere are some general tunning guideline to help you categorize the kinds of java tunning you will perform:
\n1. Be aware of ergonomics settings
\nThe -server: server compiler
\nThe -XX:+useParallelGC: parallel garbage collector
\nThe -Xms: initial heap size is 1\/64th of the machine’s physical memory
\nThe -Xmx: maximum heap size is 1\/4th of the machine’s physical memory ( up to 1 GB max)<\/p>\n
2. Heap sizing
\nThe mazimum heap size of a java application is limited by the factors:
\nThe process daata model (32-bit or 64-bit) on the system.
\nThe amount of physical memory available on the system.
\nThe size of the java heap for a paricular application can never exceed or even reach the maximum
\nvirtual address space of the process data model.<\/p>\n
3. Garbage collector policy
\nThe -XX:+UseParallelGC: parallel garbage collector
\nThe -XX:+UseConcMarkSweepGC: concurrent garbage collector (CMS)
\nThe -XX:+UseSerialGC: serial garbage collector ( for smaller applications and systems)<\/p>\n
4. Other tunning parameters
\nThe -XX:+UseLargePages: large memory pages.
\nThe -XX:LargePageSizeInBytes:<\/p>\n
Examples:
\n1. Tunning for throughput
\nHere is an example of specific command line tuning for a server application
\nrunning on system with 4 GB of memory and capable of running 32 threads simultaneously
\n(CPU’s and cores or contexts).
\njava -Xmx3800m -Xms3800m -Xmn2g -Xss128k -XX:+UseParallelGC -XX:ParallelGCThreads=20<\/p>\n
2. Try the parallel old generation collector
\nSimilar to example 1 we here want to test the impact of the parallel old generation collector.
\njava -Xmx3550m -Xms3550m -Xmn2g -Xss128k -XX:+UseParallelGC -XX:ParallelGCThreads=20 -XX:+UseParallelOldGC<\/p>\n
3. Try 256 MB pages
\nThis tuning example is specific to those Solaris-based systems that would support the huge page size of 256 MB.
\njava -Xmx2506m -Xms2506m -Xmn1536m -Xss128k -XX:+UseParallelGC -XX:ParallelGCThreads=20
\n-XX:+UseParallelOldGC -XX:LargePageSizeInBytes=256m<\/p>\n
4. Try -XX:+AggressiveOpts
\nThis tuning example is similar to Example 2, but adds the AggressiveOpts option.
\njava -Xmx3550m -Xms3550m -Xmn2g -Xss128k -XX:+UseParallelGC -XX:ParallelGCThreads=20
\n-XX:+UseParallelOldGC -XX:+AggressiveOpts<\/p>\n
5. Try Biased Locking
\nThis tuning example is builds on Example 4, and adds the Biased Locking option.
\njava -Xmx3550m -Xms3550m -Xmn2g -Xss128k -XX:+UseParallelGC -XX:ParallelGCThreads=20
\n-XX:+UseParallelOldGC -XX:+AggressiveOpts -XX:+UseBiasedLocking<\/p>\n
6.Tuning for low pause times and high throughput
\nThis tuning example similar to Example 2, but uses the concurrent garbage collector
\n(instead of the parallel throughput collector).
\njava -Xmx3550m -Xms3550m -Xmn2g -Xss128k -XX:ParallelGCThreads=20 -XX:+UseConcMarkSweepGC
\n-XX:+UseParNewGC -XX:SurvivorRatio=8 -XX:TargetSurvivorRatio=90 -XX:MaxTenuringThreshold=31<\/p>\n
7. Try AggressiveOpts for low pause times and high
\nThis tuning example is builds on Example 6, and adds the AggressiveOpts option.
\njava -Xmx3550m -Xms3550m -Xmn2g -Xss128k -XX:ParallelGCThreads=20 -XX:+UseConcMarkSweepGC
\n-XX:+UseParNewGC -XX:SurvivorRatio=8 -XX:TargetSurvivorRatio=90 -XX:MaxTenuringThreshold=31
\n-XX:+AggressiveOpts<\/p>\n
<\/p>\n
<\/p>\n
A good start to understand JVM, Heap, Perm Gen and GC collector<\/p>\n
JDK 6 Performance Features and Update
\nGC Collector:<\/p>\n
Serial Collector (-XX:+UseSerialGC)
\n\u2022 Throughput Collectors
\n> Parallel Scavanging Collector for Young Gen
\n? -XX:+UseParallelGC
\n> Parallel Compacting Collector for Old Gen
\n? -XX:+UseParallelOldGC (on by default with ParallelGC in JDK 6)
\n\u2022 Concurrent Collector
\n> Concurrent Mark-Sweep (CMS) Collector
\n? -XX:+UseConcMarkSweepGC
\n> Concurrent (Old Gen) and Parallel (Young Gen) Collectors
\n? -XX:+UseConcMarkSweepGC -XX:+UseParNewGC
\n\u2022 The new G1 Collector as of Java SE 6 Update 14 (-XX:+UseG1GC)<\/p>\n
Sample JVM Parameters:<\/p>\n
Performance Goals and Exhibits
\nA) High Throughput (e.g. batch jobs, long transactions)
\nB) Low Pause and High Throughput (e.g. portal app)
\n\u2022 JDK 6
\nA) -server -Xms2048m -Xmx2048m -Xmn1024m -XX:+AggressiveOpts
\n-XX:+UseParallelGC -XX:ParallelGCThreads=16
\nB) -server -Xms2048m -Xmx2048m -Xmn1024m -XX:+AggressiveOpts
\n-XX:+UseConcMarkSweepGC -XX:+UseParNewGC -XX:ParallelGCThreads=16
\n\u2022 JDK 5
\nA) -server -Xms2048m -Xmx2048m -Xmn1024m -XX:+AggressiveOpts
\n-XX:+UseParallelGC -XX:ParallelGCThreads=16 -XX:+UseParallelOldGC
\n-XX:+UseBiasedLocking
\nB) -server -Xms2048m -Xmx2048m -Xmn1024m -XX:+AggressiveOpts
\n-XX:+UseConcMarkSweepGC -XX:+UseParNewGC -XX:ParallelGCThreads=16
\n-XX:+UseBiasedLocking
\nRule of Thumb on Best selection of<\/p>\n
> Garbage Collector (Make sure to override GCThreads)
\n> Heap Size (-Xms == 1\/64 Max Memory or Max Heap and
\n-Xmx == \u00bc Max Memory or Max Heap)
\n> Runtime Compiler (-server vs -client)
\n\u2022 Desired Goals (This is a hint, not a guarantee)
\n> Maximum Pause Time (-XX:MaxGCPauseMillis=)
\n> Application Throughput (-XX:GCTimeRatio= where
\nApplication time = 1 \/ (1 + n))<\/p>\n
Do check out 1.5 paper as it comes with sample parameters for high thoughput and low latency application
\nJava 1.5 Tuning White Paper
\nIf you are using 1.6, check out the difference and improvement from 1.6 paper, take note that 1.5 parameters still apply to 1.6.<\/p>\n
Java SE 6 Performance White Paper<\/p>\n
A very practical and easy to understandable slide which walking you through the Sun HotSpot GC tuning tip and take-away parameters.<\/p>\n
HotSpot JVM Tuning<\/p>\n
Wondering whether java thread stack space (Xss) and perm gen (MaxPermSize) part of heap space. The answer is NO. That is why when u saw actually linux memory consumption is bigger than your “-Xmx” settings.
\nUsing -Xss to adjust Java default thread stack size to save memory and prevent StackOverflowError<\/p>\n
One working jvm parameters with JBoss server:<\/p>\n
JAVA_OPTS=”-server -Xms3072m -Xmx3072m -Xmn2048m -XX:MaxPermSize=256m -Dorg.jboss.resolver.warning=true -Dsun.rmi.dgc.client.gcInterval=3600000 -Dsun.rmi.dgc.server.gcInterval=3600000 -XX:ParallelGCThreads=8 -XX:+UseConcMarkSweepGC -XX:+UseParNewGC -XX:SurvivorRatio=8 -XX:TargetSurvivorRatio=90 -XX:MaxTenuringThreshold=31 -XX:+AggressiveOpts -XX:+PrintHeapAtGC -XX:+PrintGCTimeStamps -XX:+PrintGCDetails -XX:+PrintGCApplicationStoppedTime -Xloggc:\/opt\/jbos\/server\/default\/log\/jvmgc.log”<\/p>\n
<\/p>\n
<\/p>\n
Advanced JVM Tuning for Low Pause
\nThe standard Java Virtual Machine (JVM) is configured to optimize for throughput. But some systems are more interested in low pause\/reduced latency and GC (garbage collection) might be one source of pausing.
\n(you can read an interesting article about what latency means to your business)<\/p>\n
I have found a post on GigaSpaces forum providing some possible JVM configurations to optimize on latency:<\/p>\n
-Xms2g -Xmx2g -Xmn150m
\n-XX:+UseConcMarkSweepGC -XX:+CMSIncrementalMode
\n-XX:+CMSIncrementalPacing -XX:CMSIncrementalDutyCycleMin=10
\n-XX:CMSIncrementalDutyCycle=50 -XX:ParallelGCThreads=8
\n-XX:+UseParNewGC -XX:MaxGCPauseMillis=2000
\n-XX:GCTimeRatio=10 -XX:+DisableExplicitGC
\nPlease note that -XX:+UseConcMarkSweepGC has the heaviest impact on performance \u2013 decrease of 40%.<\/p>\n
The following set of parameters shows 20% better performance than with -XX:+UseConcMarkSweepGC while the pause size still is below 100msec in embedded test with payload 10KB and 100 threads:<\/p>\n
-Xms2g -Xmx2g -Xmn150m
\n-XX:GCTimeRatio=2 -XX:ParallelGCThreads=8
\n-XX:+UseParNewGC -XX:MaxGCPauseMillis=2000
\n-XX:+DisableExplicitGC
\nWhile I\u2019m pretty sure that most of the applications do no need such an advanced VM configuration, it is interesting to see what strategies are employed when low latency is needed.<\/p>\n
Option Details
\n-XX:+UseConcMarkSweepGC Sets the garbage collector policy to the concurrent (low pause time) garbage collector (also known as CMS)
\n-XX:+CMSIncrementalMode Enables the incremental mode. (works only with -XX:+UseConcMarkSweepGC)
\n-XX:+CMSIncrementalPacing Enables automatic adjustment of the incremental mode duty cycle based on statistics collected while the JVM is running
\n-XX:CMSIncrementalDutyCycleMin The percentage (0-100) which is the lower bound on the duty cycle when CMSIncrementalPacing is enabled
\n-XX:CMSIncrementalDutyCycle The percentage (0-100) of time between minor collections that the concurrent collector is allowed to run. If CMSIncrementalPacing is enabled, then this is just the initial value.
\n-XX:ParallelGCThreads Sets the number of garbage collector threads
\n-XX:+UseParNewGC Enables multi threaded young generation collection.
\n-XX:MaxGCPauseMillis A hint to the throughput collector that it\u2019s desirable that the maximum pause time is lowed than the given value. (n.b. it looks like this value can also be used with the CMS garbage collector)
\n-XX:GCTimeRatio A hint to the virtual machine that it\u2019s desirable that not more than 1 \/ (1 + GCTimeRation) of the application execution time be spent in the collector
\n-XX:+DisableExplicitGC Disables explicit garbage collection calls (System.gc())
\nThere is no need to learn all these flags by heart as you can find them covered in various documents:<\/p>\n
<\/p>\n
<\/p>\n
<\/p>\n
<\/p>\n
Custom settings was:<\/p>\n
-Xms768m
\n-Xmx768m
\n-XX:NewSize=128m
\n-XX:MaxNewSize=128m
\n-XX:+UseParNewGC
\n-XX:ParallelGCThreads=8
\n-XX:MaxTenuringThreshold=1
\n-XX:SurvivorRatio=8
\n-XX:+UseConcMarkSweepGC
\n-XX:+CMSParallelRemarkEnabled
\n-XX:CMSInitiatingOccupancyFraction=65
\n-XX:+CMSScavengeBeforeRemark
\n-XX:+UseCMSInitiatingOccupancyOnly
\n-XX:MaxPermSize=250m
\n-XX:ReservedCodeCacheSize=64m<\/p>\n","protected":false},"excerpt":{"rendered":"
The general tuning guidelines for java VM. Here are some general tunning guideline to help you categorize the kinds of java tunning you will perform: 1. Be aware of ergonomics settings The -server: server compiler The -XX:+useParallelGC: parallel garbage collector The -Xms: initial heap size is 1\/64th of the machine’s physical memory The -Xmx: maximum […]<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[46],"tags":[],"_links":{"self":[{"href":"https:\/\/mohan.sg\/index.php?rest_route=\/wp\/v2\/posts\/2089"}],"collection":[{"href":"https:\/\/mohan.sg\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/mohan.sg\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/mohan.sg\/index.php?rest_route=\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/mohan.sg\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=2089"}],"version-history":[{"count":6,"href":"https:\/\/mohan.sg\/index.php?rest_route=\/wp\/v2\/posts\/2089\/revisions"}],"predecessor-version":[{"id":2635,"href":"https:\/\/mohan.sg\/index.php?rest_route=\/wp\/v2\/posts\/2089\/revisions\/2635"}],"wp:attachment":[{"href":"https:\/\/mohan.sg\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=2089"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/mohan.sg\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=2089"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/mohan.sg\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=2089"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}