Download PDF (1.3 MB) - IBM Redbooks

4.16.2 Setting the heap size for most configurations
This section contains guidelines for determining the appropriate Java heap size for most
configurations. If your configuration requires that more than one JVM run concurrently on the
same system, see 4.16.3, “Setting the heap size when running multiple JVMs on one system”
on page 94. For example, you might need more than one JVM if you run both a Business
Process Manager server and Integration Designer on the same system. If your objective is
designed to support large business objects, read 4.7.2, “Tuning for large objects” on page 63.
When the heap size is too low, OutOfMemory errors occur. For most production applications,
the IBM JVM Java heap size defaults are too small, so increase them. When the heap size is
too low, OutOfMemory errors occur. In general, the HotSpot JVM default heap and nursery
size are also too small so increase them also.
There are several approaches to setting optimal heap sizes. Here we describe the approach
that most applications can use when running the IBM JVM on AIX. The essentials can be
applied to other systems. Set the initial heap size (-Xms option) to a typical value (for example,
768 MB on a 64-bit JVM, or 256 MB on a 32-bit JVM). Set the maximum heap size (-Xmx)
option to a typical value, but large (for example, 3072 MB on a 64-bit JVM, or 1024 MB on a
32-bit JVM). The maximum heap size must never force the heap to page. The heap must
always stay in physical memory. The JVM then tries to keep the GC time within reasonable
limits by growing and shrinking the heap. The output from verbosegc is used to monitor
garbage collection (GC) activity.
If Generational Concurrent GC is used (-Xgcpolicy:gencon), you can also set the new area
size to specific values. By default, the new size is a quarter of the total heap size or 64 MB,
whichever is smaller. For better performance, set the nursery size to half of the heap size or
larger, and do not cap the value at 64 MB. You can set new area sizes by using the following
JVM options:
► -Xmn
► -Xmns
► -Xmnx
You can use a similar process to set the size of HotSpot heaps. In addition to setting the
minimum and maximum heap size, also increase the nursery size to a range of 1/4 to 1/2 of
the heap size. Never increase the nursery to more than half the full heap.
You can set the nursery size by using the MaxNewSize and NewSize parameters:
► -XX:MaxNewSize=128m
► -XX:NewSize=128m
If you are using a 64-bit IBM JVM, use the -Xgc:preferredHeapBase parameter to avoid native
out-of-memory issues because of exhaustion of memory addresses below 4 GB (for example,
classes and threads are allocated in this region). The -Xgc:preferredHeapBase option can be
used to move the Java heap outside of the lower 4 GB address space. See the IBM JVM
information center for a more detailed description of the solution:
http://ibm.co/10CGjeT
After the heap sizes are set, use verbosegc traces to monitor GC activity. After analyzing the
output, modify the heap settings accordingly. For example, if the percentage of time in GC is
high and the heap has grown to its maximum size, you might improve throughput by
increasing the maximum heap size. As a general guideline, greater than 10% of the total time
spent in GC is generally considered high.
Chapter 4. Performance tuning and configuration 93