Customers often ask about the proper heap size setting for LiveCycle ES2. The answer quite often is “it depends”. However, an interesting set of eight, one-hour tests indicate that at least for the eTech LiveCycle Benchmark, the memory sweet spot is about 5 GB. The test hardware was a Dell Precision 690 Workstation with 12 GB of RAM, and two dual-core (4 cores total) Intel Xeon 5160 “Woodcrest” 3.0 GHz CPUs. Test software was LiveCycle ES2 SP2/JBoss 4.2.1/Windows Server 2008/Oracle 11g.
The default memory configuration for the pre-configured JBoss tree that LiveCycle ES2 ships with is the following:
-Xms1024m -Xmx1792m -XX:PermSize=256m -XX:MaxPermSize=384m
The throughput achieved with this configuration was 4,862 (transactions/hr with 10 concurrent users).
However, by increasing heap size in steps as well as by configuring garbage collection, we were able to achieve a throughput of 5,709 at a heap size setting of 5 GB. Please see the profile below.
The memory configuration was as follows:
-Xms5120m -Xmx5120m -XX:PermSize=512m -XX:MaxPermSize=512m
The garbage collection configuration was as follows:
-XX:+UseParallelGC -XX:+UseParallelOldGC -XX:ParallelGCThreads=4 -XX:NewRatio=1 -XX:MaxTenuringThreshold=100