High VSS or VIRT memory by cybAgent.bin pocess

Products

• Workload Automation Agent
• CA Workload Automation DE - System Agent (dSeries)
• CA Workload Automation DE - System Agent (dSeries)
• CA Workload Automation AE - System Agent (AutoSys)
• CA Workload Automation DE - Business Agents (dSeries)

Issue/Introduction

Why cybAgent.bin process takes High VSS/VIRT memory 

PID    USER  PR  NI   VIRT    RES    SHR  S  %CPU %MEM    TIME+     COMMAND
24081  root  20  0    39.9g   128m   13m  S   0.3  0.8    0:02.07   cybAgent.bin 

Environment

This is observed in Linux OS.

Resolution

VSS field reflects reserved virtual memory only and it does not indicate actual memory allocation.  For more details, consult Linux documentation.

The WA Agent memory usage is shown in the simple_health_monitor.log.  The simple_health_monitor.log has below three numbers:

• Maximum allocatable - the reserved memory addresses (this will be the maximum that the program will ever try to allocate, if needed) 
• Total allocated heap - the memory actually allocated from system memory 
• Currently free heap - the amount of the allocated heap that can be used by the program before more memory needs to be allocated. 

The maximum allocatable memory used by the System Agent can be controlled by setting an agentparm.txt setting.
For example, to set the maximum allocatable memory to 512 MB, add the following to the agentparm.txt file: 

oscomponent.jvm.x.options=-Xmx512M