Resolve EngageOne Core and Security services reaching 2 GB in idle state in EngageOne 4.3

Product Feature: Administration



Without any operation being performed 'Private working set' (as shown in task manager) of the executables can reach upto 2 GB.

User-added image 


Processes take 2 GB of memory as during installation (via it was configured to consume approximately 2 GB memory on startup.
The parameter governing this configuration are defined under Refer

# Java Virtual Machine settings.
# Defaults:
#    core.jvm.settings=-Xms2g -Xmx4g -XX:MaxPermSize=512M
#    security.jvm.settings=-Xms4g -Xmx4g -XX:MaxPermSize=256m -XX:PermSize=256m -XX:+UseConcMarkSweepGC -XX:+DisableExplicitGC -XX:NewSize=1333m -XX:MaxNewSize=1333m

Security and Core have been defined for 'Xms2g -Xmx4g' hence it will always occupy 2 GB initially and can go upto 4 GB if needed. Java processes usually do not force garbage collection if not needed, so resources stay taken and hence memory is occupied. 

Please note "Hardware Requirements" in documentation  describes 6GB RAM for each bundle.


UPDATED: April 21, 2017
In case it is required to lower the configuration, set '-Xms' to 1GB and '-Xmx'  to 2GB. It will always allocate/reserve 1GB because of configuration '-Xms' and it will grow up to 2GB as that is maximum value allowed to use via '-Xmx'. When approaching 2GB it will try to clean unwanted memory.