You may want to add the following JVM tuning parameters to the JAVA_OPTS
in the bin/run.conf
(UNIX) or run.bat
(Windows) file:
-Dtomcat.util.buf.StringCache.byte.enabled=true
Enables the byte array to String conversion caching.
-Dtomcat.util.buf.StringCache.char.enabled=true
Enables the char array to String conversion caching.
-Dtomcat.util.buf.StringCache.trainThreshold=5
The cache is built after a training period, during which statistics about converted Strings are kept. The value of this property specifies the number of String conversions to perform before building the cache.
-Dtomcat.util.buf.StringCache.cacheSize=2000
The maximum number of String objects that will be cached, according to their usage statistics.
The effectiveness of the StringCache can be checked using the JMX-Console. Look for StringCache under Catalina in the JMX-Console page.
For the JVM command-line, the following settings can be used:
Memory set at just over 1G for each server
MaxPermSize adjusted to 256m
If you are using JDK 1.4, you may want to experiment with the garbage collection settings to see what gives you the best performance. This is not necessary with JDK 1.5.