Confluence : Managing Application Server Memory Settings
This page last changed on Apr 13, 2007 by david.soul@atlassian.com.
The minimum and maximum JVM heap space allocated to the application server affects performance. Confluence administrators may wish to modify this value from the defaults depending on their server load. This document only provides guidelines rather than rules, so administrators optimising for performance should use this document as a starting point only. Testing For Optimum Memory SettingsBigger is not always better for heap size. When optimising memory settings, consider starting by setting the maximum heap size to 1/4 the available physical memory on the server and setting the minimum to 1/2 of the maximum heap. Avoid setting the minimum and maximum to be the same since server load is normally variable. Being able to use less memory under low load results in slightly improved performance as garbage collections can be made smaller. Testing Resources
Determine Minimum Memory Determine Maximum Memory
The maximum memory should be the total memory while in this state plus a buffer of at least 15%, taking into account how your garbage collection performs. Never set maximum memory to a value above 85-90% of the available physical server memory as this results in disk paging. Always leave 10-15% of available physical server memory unallocated to allow for OS background processes. Applying Memory SettingsUsers of the EAR/WAR version set their memory in their application server. For Confluence Standalone, the heap space is set in the Confluence install directory.
The relevant parameter is JAVA_OPTS="-Xms128m -Xmx256m ... " Where -Xms is the minimum and -Xmx is the maximum memory available to Apache Tomcat. Related Topics |
![]() |
Document generated by Confluence on May 01, 2007 19:29 |