If you are a Managed Hosting customer, this topic doesn't apply to you.

The Java Object Heap (Java Heap) stores Java objects, including instances of classes and the data that the objects contain, such as primitives and references. The amount of memory allocated to the JVM as a whole and to its individual regions is different for every Blackboard Learn deployment. As with the maximum thread count value for Tomcat, the appropriate size of the Java Heap will vary depending on application usage.

JVM's built-in GC logging options, and tools like JConsole, VisualVM, dynaTrace, New Relic, and AppDyanmics can be used to determine the actual memory usage and management.

On 64-bit deployments, Blackboard recommends initially sizing the Java Heap to a value between 4GB and 8GB. Some customers have deployed substantially larger JVMs than 8GB with success. If the memory resources continue to become saturated after increasing the heap size, consider adding additional JVMs. Additional non-standard HotSpotoptions can also be applied to improve overall memory throughput and management. To learn more about the JVM options supported by Java, see http://java.sun.com/javase/technolog.../vmoptions.jsp.