Join the Conversation
- Find Answers
- :
- Splunk Products
- :
- Splunk AppDynamics
- :
- Re: Memory usage for Windows machine agent and dat...
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark Topic
- Subscribe to Topic
- Mute Topic
- Printer Friendly Page
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello,
We are planning to deploy a standalone machine agent and database agent (v4.5.17) but the memory usage is too high:
Machine agent: 1GB
Database agent: 620MB
We are trying to fine-tune the java options in the vmoptions files. In order to reduce the memory footprint with these values:
-XX:MaxPermSize=10m ==> 20MB seems to be the default
-Xmx32m ==> 256 MB to be the default
-Xms2m
-Xss32m
With these settings, the Machine agent seems stable with 250MB and db agent with 150MB.
Has anyone done this on production servers?
Regards,
Thierry QUESSADA
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello,
I opened a case to the support and the requirements of memory for these agents are huge.
https://docs.appdynamics.com/display/PRO45/Database+Visibility+System+Requirements
It seems there is no way to reduce the memory footprint of these two agents with a bundled JRE.
Because of this behavior, the machine agent seems to be worthless and the DB agent will be installed on a dedicated server.
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hi. Supposedly there was an issue with Windows itself that introduced the memory issue. Please use the latest updated machine agent where that problem should be resolved. Let me know if that still doesn't work.
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Thank you for you answer ,
The 4.5.18 seems to be the lastet version.
I'd rather not install a version too young on production.
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Hello,
I opened a case to the support and the requirements of memory for these agents are huge.
https://docs.appdynamics.com/display/PRO45/Database+Visibility+System+Requirements
It seems there is no way to reduce the memory footprint of these two agents with a bundled JRE.
Because of this behavior, the machine agent seems to be worthless and the DB agent will be installed on a dedicated server.
Join the Splunk Community Slack to learn, troubleshoot, and make connections with fellow Splunk practitioners in real time!
Join Splunk User Groups to connect and learn in-person by region or remotely by topic or industry.
Announcing Modern Navigation: A New Era of Splunk User Experience
Modernize your Splunk Apps – Introducing Python 3.13 in Splunk
Step into “Hunt the Insider: An Splunk ES Premier Mystery” to catch a cybercriminal ...
