Configuring for Optimal Performance
BEA AquaLogic Commerce Services Deployment Guide 49
• velocity.xml - It is very important that you have configured Velocity for production
according to these instructions.
• util-config.xml - It is very important that you have configured Velocity for production
according to these instructions.
• ep-treecache.xml - You can tweak cache settings in this file to tune your performance
(Storefront only).
• hibernate-config.xml - Check that "show SQL" is off. You can also tweak the commit batch
size to tune import manager performance.
• quartz.xml - Check this file to ensure that you are not running batch jobs during peak times or
during performance tests.
Performance tip
Check that you have configured Velocity for production by following the
instructions in velocity.xml and especially util-config.xml.
Run your JVM in server mode
The JVM server mode will take longer to start but performs better once it is running. Use server
mode for production environments and client mode for development only.
Specify the JVM heap size
By default, a JVM may only be able to use 64M or 128M memory.
You should specify the heap size of the application server JVM to make more memory accessible
to it.
• -Xms specifies the initial Java heap size
• -Xmx specifies the maximum Java heap size
Sample setting:
-Xmx4096m -Xms4096m
Linux Memory Limitation
In 32bit Linux, the JVM may only be able to use up to 2GB memory.
Use a different garbage collector
In JVM version 1.5, several types of garbage collectors are provided. On a 2-CPU server, our test
results show that the concurrent low pause collector gives a little better performance under stress.
Application Server
• Shorten the session timeout
If you define a long session timeout, data stored in the session have a higher chance of being
pushed up into slower segments of the JVM memory where they are expensive to garbage
collect. Shorter timeouts will also increase the amount of memory available.
