This topic has not yet been written. The content below is from the topic description.
2.1 Heap Sizing Heap sizing is an important aspect of setting up your environment. Set it too low and your application will throw OutOfMemoryExceptions as well as not function very well. Set it too high and you may not use it / may not be able to scale your system accordingly. How large you should set your heap depends largely on your application. As a baseline, if you are using JBoss EAP with the all configuration (all services enabled, not recommended for production), the application server by itself will need about 512Mb of memory during startup to initialize properly. Once it is started, it will run within about 300Mb. With that in mind, setting your heap to anything less than 512Mb will be problematic and your application server won’t start up. The production profile does have a lighter footprint and you can of course slim your environment down even further, but this should give you some sense of a baseline. To modify your heap size, you will want to modify the conf file used when starting your JBoss EAP instance – run.conf. Most notably in this file are the -Xms and -Xmx settings. These set the max and min values of your heap. Setting these values the same is a standard practice as that way there is no need for the JVM to go get more memory space, it is all allocated right upfront. Modifying these values is as simple as A more detailed view on Heap and how it correlates with garbage collection can be found here – http://www.oracle.com/technetwork/java/gc-tuning-5-138395.html