RAM requirements for host servers are listed in CAST AIP for Dashboards - Hardware requirements, however, "out of the box", the Windows Services and batch scripts made available to run the AIP Console (front-end) and AIP Nodes (which are Java applications) are configured to run with conservative RAM memory allocations as shown in the table below:
|Xmx value||1024MB||Maximum memory allocation pool for a Java Virtual Machine (JVM).|
|Xms value||256MB||Initial memory allocation pool for a Java Virtual Machine (JVM).|
This means that even though the host server may have 64GB RAM available (for example), it will only give a maximum of 1GB to the JVM in which AIP Console and the AIP Nodes run. You may therefore find that this is not sufficient and you may receive low memory/out of memory errors when running analyses or snapshots. If this is the case, CAST recommends increasing the Xmx and Xms values until your low memory/out of memory exceptions have been resolved as explained below.
CAST highly recommends using the following values in "large" deployment scenarios, for both AIP Console front-end and all AIP Nodes:
Modifying Windows Services memory settings
- Stop the AIP Console or AIP Node Windows Services
- Execute the following executable on the host server depending on your requirements:
The following configuration screen will be displayed. Click the Java tab (1) and make your changes as highlighted (2):
Click Apply and then OK to confirm the modification to the JVM memory settings, then restart the Windows Service to use the new settings.
Modifying default batch scripts
If you are using the default batch scripts to start the AIP Conseol (front-end) or the AIP Nodes, then you should modify the following files after having stopped the running service:
Locate the line containing the Xmx and Xms values and modify it as required. For example, for an AIP Node:
Save the file and then restart the relevant service.