Previous releases of the Management Console for Unix used Java 6 and tended to require manual tuning of the JVM memory settings. Java 8 reduces the need for this because, by default it automatically chooses its initial and maximum heap sizes as fractions of the host's memory size. The resulting maximum heap size can be displayed by running this command:
java -XshowSettings:vm -version
However, there may still be scenarios for which manual tuning is desirable. If you are experiencing performance degradation due to heavy demand from web service calls, simultaneous report generation, multiple browser connection querying, and so forth, One Identity recommends that you increase the JVM memory.
To tune JVM memory
Open the custom.cfg file for editing.
See Setting custom configuration settings for general information about customizing configuration settings for the mangement console.
Set the initial or start memory size using the -Xms variable and the maximum memory size using the -Xmx variable. For example:
where "512m" specifies 512MB of memory or "1g" specifies 1GB of memory.
Note: 1024MB is the default memory requirement.
One Identity recommendations:
These suggested specifications depend on your reporting demands. If you create more than two or three reports simultaneously, increase the memory specification.
For further information on specific settings refer to <install_directory>/jvmargs.cfg
These values are used for the JVM heap which reserves memory for the server and its database. Increasing the amount of memory available can improve performance, but increasing it too much can have a detrimental effect in the form of longer pauses for full garbage collection runs. Setting -Xms and -Xmx to the same value increases predictability by removing the most important sizing decision from the virtual machine. On the other hand, the virtual machine cannot compensate if you make a poor choice. Be sure to increase the memory as you increase the number of processors, since allocation can be parallelized. JVM heaps greater than 1.5 Gbytes require a 64-bit JVM. Anything more than that will cause the service to not start.
Numbers can include 'm' or 'M' for megabytes, 'k' or 'K' for kilobytes, and 'g' or 'G' for gigabytes. For example, 32k is the same as 32768. Unless you have problems with pauses, try granting as much memory as possible.
For further reading on garbage collection tuning refer to https://docs.oracle.com/javase/8/docs/technotes/guides/vm/gctuning/.
Save the custom.cfg file.
Restart the Management Console for Unix service.
See Start/stop/restart Management Console for Unix service for details about restarting the Management Console for Unix Service.
Depending on the platform you are using, use the corresponding procedure to start, stop, or restart the Management Console for Unix service (mcu_service).
To stop, start, or restart the Management Console for Unix service (mcu_service) on a Linux/Solaris machine
To stop and restart the service automatically:
To stop the service and unload it:
To load the service and start it:
To stop, start, or restart the Management Console for Unix service (mcu_service) on an HP Unix machine
To stop and restart the service automatically, enter:
To stop the service and unload it, enter:
To load the service and start it, enter: