Configuration When MashZone NextGen Uses Heap and Off-Heap Memory

Integrate Software AG Products Using Digital Event Services : MashZone NextGen Help : Appendix : Administration : MashZone NextGen Server Configuration : Memory Configuration for the MashZone NextGen Server : Configuration When MashZone NextGen Uses Heap and Off-Heap Memory

MashZone NextGen should be configured to use both heap and off-heap memory only when the available memory supports this adequately and you have also installed BigMemory Servers.

Note:

You must have installed a copy of your BigMemory license in MashZone NextGen to use off-heap memory. See Manage Licenses for MashZone NextGen and BigMemory for instructions.

With combination heap and off-heap memory, as this figure shows, BigMemory uses off-heap memory for the MashZone NextGen Analytics In-Memory Stores and MashZone NextGen caches. All other MashZone NextGen processing, including the Event Service that is deployed with MashZone NextGen, remains in heap.

The total available off-heap memory may be limited to local off-heap memory as shown above, or it may include additional off-heap memory on external hosts if you have installed BigMemory Server arrays.

To update memory configuration:

1. In a text editor of your choice, open the application server configuration file MashZoneNG-install/apache-tomcat/conf/wrapper.conf.

2. Change or add either of these memory options used with BigMemory:

wrapper.java.additional.<n+1>

=-Dpresto.bm.maxOffHeap

Default = 1G

Where n is the number of last additional Java parameter.

This is the maximum size of local off-heap memory that BigMemory can use for the MashZone NextGen Analytics In-Memory Stores and MashZone NextGen caches.

This property sets off-heap memory limits in the MashZoneNG-config/ehcache.xml configuration file. The total size of off-heap memory may include additional, external memory depending on how BigMemory is deployed.

wrapper.java.additional.<n+2>

=-XX:MaxDirectMemorySize

Default = 1500M

Where n is the number of last additional Java parameter.

This Java memory option must be set to allow access to both off-heap and an additional allocation for Java.

The value of this option must always be larger than the memory allocated to off-heap. A good rule of thumb is at least 500M more.

3. Change or set any of these Java memory options:

wrapper.java.initmemory	Default = 512M
wrapper.java.maxmemory	Default = 2G

See the Java Tuning White Paper for more information and suggestions.

4. Save your changes and restart the MashZone NextGen Server. See Start and Stop the MashZone NextGen Server for instructions.

Contact Support | Community | Feedback