The memory in the jvmargs file is set to 3GB, but the Foglight Agent Manager (FglAM) process still consumes about 6GB.
Why is it consuming more memory than set and what is the memory footprint of the FglAM?
The additional JVM heap size is due to deployments that are using the agent resource negotiation.
The startup heap size is -Xmx4718592k which is a combination of the base FglAM memory requirements, heap settings in the baseline-jvmargs.config and any deployment memory resource requests.
The startup heap size request can be seen as a sum of all these values in file "$FglAM_HOME/state/default/config/deployment/vm.deployments.config".
NOTE: It is auto generated, so please do not try changing values here. It is just for reference and rounding out the explanation of where these settings are stored.
The VMwarePerformance agent package requests 2G of heap on deployment. That coupled with the 2GBs from the baseline-jvmargs.config file gets us close to the heap size the FglAM is using.
