Tune Memory/Caching for the Integrated MashZone Server
MashZone NextGen, the Integrated
MashZone Server and the
Event Service share the local Java heap memory. Heap memory is also used for internal caches and
MashZone NextGen In-Memory Stores used in
MashZone NextGen Analytics.
MashZone NextGen can also be configured to use off-heap memory if you have installed
BigMemory Servers. For more information, see
Memory Configuration for the
MashZone NextGen
Server and About
BigMemory and
the
MashZone NextGen
Analytics In-Memory Stores.
The Integrated MashZone Server and the Event Service are initially installed based on assumptions for a small web application. This default memory allocation may work well for development environments, but may need to be adjusted for staging or production environments. Memory requirements for MashZone NextGen, the MashZone NextGen In-Memory Stores and event sources in the Event Service may also affect the overall available memory, requiring tuning for MashZone internal caches.
You may adjust configuration for both Java heap memory and memory configuration for the internal caches used by the Integrated MashZone Server using the following techniques:
Manual tuning gives you greater control to balance memory requirements for MashZone NextGen, the Integrated MashZone Server and the Event Service, but does require manual updates to several configuration files.
This uses a simple script to automatically update memory and cache configuration based on preset sizes. These preset values, however, do not take any memory requirements for MashZone NextGen or MashZone NextGen In-Memory Stores into account and thus may not be suitable in some circumstances.
Tune
MashZone
Memory and Cache Configuration Manually.