Supporting a greater number of concurrent sessions in Ignite
When you are using Ignite as the cache manager in some Unica Interact environments, a high number of concurrent
sessions may cause the Unica Interact runtime to
exceed its available memory, causing a system slowdown or out-of-memory error. An out-of-memory
situation is more likely if you have increased the maxEntriesInCache
configuration
parameter (Unica Interact >
cacheManagement > Caches > InteractCache > maxEntriesInCache) to a number higher than
the default setting, although it can occur even with the default setting of a maximum of 100,000
sessions. To avoid this issue, you can reduce the maxEntriesInCache value, or
you can follow the instructions here to modify the system memory cache to roll the cached memory
over to disk storage. This modification allows many more concurrent sessions than would otherwise be
possible.
To prevent the Unica Interact runtime from exceeding the available memory in the Java™ virtual machine (JVM) memory heap, you can modify the memory caching mechanism to use disk storage for caching the data that exceeds the available memory.
However, enabling disk storage will cause a performance degradation. System administrators can adjust the amount of memory available to the deployment systems via the following JVM parameters:
-Xms####m -Xmx####m -XX:MaxPermSize=256m
where the characters #### should be 2048 or higher (depending on their system load.)