Splunk AppDynamics

Limiting machine agent memory utilization

CommunityUser
Splunk Employee
Splunk Employee

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

Labels (1)

Gareth_Humphrie
Engager

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

Paul_Szoke
Explorer
Has there been any response or solution provided to this?
0 Karma

iamryan
Community Manager
Community Manager

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.

0 Karma
Get Updates on the Splunk Community!

Pro Tips for First-Time .conf Attendees: Advice from SplunkTrust

Heading to your first .Conf? You’re in for an unforgettable ride — learning, networking, swag collecting, ...

Raise Your Skills at the .conf25 Builder Bar: Your Splunk Developer Destination

Calling all Splunk developers, custom SPL builders, dashboarders, and Splunkbase app creators – the Builder ...

Hunt Smarter, Not Harder: Discover New SPL “Recipes” in Our Threat Hunting Webinar

Are you ready to take your threat hunting skills to the next level? As Splunk community members, you know the ...