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
Got questions? Get answers!

Join the Splunk Community Slack to learn, troubleshoot, and make connections with fellow Splunk practitioners in real time!

Meet up IRL or virtually!

Join Splunk User Groups to connect and learn in-person by region or remotely by topic or industry.

Get Updates on the Splunk Community!

Announcing Modern Navigation: A New Era of Splunk User Experience

We are excited to introduce the Modern Navigation feature in the Splunk Platform, available to both cloud and ...

Modernize your Splunk Apps – Introducing Python 3.13 in Splunk

We are excited to announce that the upcoming releases of Splunk Enterprise 10.2.x and Splunk Cloud Platform ...

Step into “Hunt the Insider: An Splunk ES Premier Mystery” to catch a cybercriminal ...

After a whole week of being on call, you fell asleep on your keyboard, and you hit a sequence of buttons that ...