These instructions are for Ignite PI versions 4.3 and below.
If monitoring a large number of instances, it may be necessary to increase the amount of memory that is allocated to Ignite. By default, Ignite will take a minimum of 128MB but is allowed to grow to 512MB. On systems with more than 20 monitored instances, it usually makes sense to bump this up to a maximum of 1GB.
Windows Instructions (for Ignite PI Server running as a Windows service)
- Edit the file iwc\tomcat\bin\service.bat.
- Search the file for the string "--JvmMx" . It will likely be followed by "0x200". This is hexidecimal for 512.
- Change it to 0x300 to increase the maximum to 756MB. Change it to 0x400 to increase the maximum to 1GB.
- Recreate the Ignite PI Server service by running 2 batch files that were installed with Ignite PI:
- removeWindowsService.bat
- createWindowsService.bat
Windows Instructions (for Ignite PI Server running in a window)
- Edit the file iwc\tomcat\bin\catalina.bat.
- Search the file for the string "-Xmx". It will likely be followed by "512m" (for 500MB).
- Change it to "-Xmx756m" to increase the maximum to 756MB. Change it to "-Xmx1000m" to increase the maximum to 1GB.
- Restart the Ignite PI Server by running 2 scripts that were installed with Ignite PI:
Unix/Linux Instructions
- Edit the file iwc\tomcat\catalina.sh
- Find the line "set JAVA_OPTS=%JAVA_OPTS% -Xms128m -Xmx512m" and change 512m to 1024m
- Restart the Ignite PI Server by running 2 scripts that were installed with Ignite PI: