Jobs slow to execute on agent

Products

Autosys Workload Automation

Issue/Introduction

Jobs targeted to run on a specific AutoSys System Agent may experience processing delays or appear slow to initialize and execute. To address this performance lag and optimize JVM performance, it is recommended to explicitly define a maximum heap limit for the Java Runtime Environment (JRE) utilized by the agent process.

Environment

AutoSys Workload Automation 24.2
AutoSys Workload Automation System Agent 24.2

Cause

By default, newer 64-bit Java Runtime Environments bundled with the System Agent do not enforce a strict upper limit on Java heap allocation unless explicitly specified. The JVM may automatically default its maximum allocatable heap to a significant portion of the machine's total physical memory (e.g., up to one-fourth). This lack of a defined boundary or a very low/high initialization configuration can lead to sub-optimal memory utilization, garbage collection delays, or overall execution slowness.

Resolution

To adjust the Java memory usage boundaries and resolve execution slowness, configure a fixed maximum heap threshold by modifying the agent parameters:

Navigate to the agent installation directory.
Open the agentparm.txt configuration file in a text editor.
Locate or add the parameter oscomponent.jvm.x.options.
Define the maximum heap limit option (-Xmx128M) as follows:
```
oscomponent.jvm.x.options=-Xmx128M
```
Save and close the agentparm.txt file.
Restart the AutoSys System Agent service for the configuration changes to take effect.

Additional Information

Additional Information:

For general guidance on managing and setting heap boundaries within the agent, you can reference existing Article ID 39434 : How to set heap size for the CA WA Agent.
To read more on why later Java Runtime Environments consume larger amounts of default memory and how to analyze allocation, see Article ID 190473 : High Memory Utilization By System Agent

Next Steps / Related Suggestions

Health Monitoring: After implementing the change, check the simple_health_monitor.log inside the agent's log directory to verify the updated "Maximum allocatable" value and ensure the agent has stabilized.
Complex Plugin Check: If this agent executes resource-heavy extensions (such as the SAP plugin or complex Database jobs), monitor whether 128MB is sufficient or if the heap needs to be tuned higher (e.g., -Xmx256m or -Xmx512m) as detailed in Article ID 39434.

To speak with a customer representative or a Support Engineer see Contact Support. Scroll to the bottom of the page and click on the respective region.