Performance Tuning for Oracle WebCenter Content 11g - Fishbowl ...

In WebCenter Content 11g, the content management solution is deployed inside Weblogic Server (WLS), with any
JVM tuning performed on the application server. You have full control, either by modifying the managed server
using the administrative console or modifying the USER_MEM_ARGS environment variable startup scripts.
Oracle’s documentation suggests the following on Unix and Windows with the JRockit JVM:
-Xms256m -Xmx1024m –XnoOpt
The –Xmx flag specifies the maximum heap size with this example specifying 1GB of memory. Best practice is to
keep your JVM heap settings under 75-80% of the available physical RAM, within limits for machines with
excessive amounts of memory. As heap size is increased, CPU load will also increase for larger garbage collections.
Under 32-bit operating systems, 1.5GB is the practical maximum limit assuming other services are not consuming
resources.
The –Xms flag specifies the minimum heap size on initial startup. Increasing the heap takes considerable time, so it
is best to set the Xmx and Xno parameters to the same size. For example:
-Xms1024m -Xmx1024m -XnoOpt -XgcPrio:throughput
On x86 and x64 hardware, JRockit should be the preferred JVM. JRockit was a Java virtual machine optimized for
x86 hardware by Intel, purchased by BEA, and acquired by Oracle. The JRockit JVM performs significantly faster
on x86 or x64 Windows and Linux architectures than Sun’s architecturally neutral JVM implementation.
An example of JVM tuning, from another Oracle whitepaper, started with:
-Xms3g
-Xmx3g
-XX:PermSize=512m
-XX:MaxPermSize=512m
-XX:+UseParallelGC
-XX:ParallelGCThreads=8
-verbose:gc
-XX:+PrintGCDetails
-XX:+PrintGCTimeStamps
-XX:NewRatio=3
-XX:+UseAdpativeSizePolicy
-XX:+AggressiveHeap
-XX:+DisableExplicitGC
-Xnoclassgc
-Xloggc:
and continued to tune WebCenter as:
-d64
-server
-Xms3g
-Xmx3g
-XX:PermSize=512m
-XX:MaxPermSize=1024m
-XX:+AggressiveOpts
-XX:+UseParallelGC
-XX:ParallelGCThreads=16
© 2012. Fishbowl Solutions, Inc.