Limiting machine agent memory utilization
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-18-2017 11:02 AM - last edited on 09-30-2019 03:49 PM by Ryan.Paredez
Hi Team,
Could someone help me with limiting the memory utilized by AppDynamics machine agent to 100MB. I tried starting the machine agent with Xms and Xmx parameter like below, but that did not help in limiting the memory used by machine agent.
nohup java -jar /appdynamics/machine-agent/machineagent.jar -Xmx100m -Xms64m &
Thanks,
Santosh
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-23-2019 03:16 AM
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-24-2019 12:52 PM
Hello,
I found some documentation.
That states this:
The lightweight Standalone Machine Agent consumes minimal resources of your computer.
AppDynamics recommends the following additional Heap and PermGen space to accommodate the agent:
- Maximum heap size (-Xmx): 100 MB
- Maximum PermGen heap size (-XX:MaxPermSize): 20 MB
Looks similar to what you tried, but perhaps it may help.
Thanks,
Ryan, Cisco AppDynamics Community Manager
Found something helpful? Click the Accept as Solution button to help others find answers faster.
Liked something? Click the Thumbs Up button.
Check out Observabiity in Action
new deep dive videos weekly in the Knowledge Base.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-15-2021 05:46 PM
Make sure you pass the options before specifying the jar. e.g.:
$ java -Xmx100m -Xms64m -jar /appdynamics/machine-agent/machineagent.jar
Instead of
$ java -jar /appdynamics/machine-agent/machineagent.jar -Xmx100m -Xms64m