Splunk AppDynamics
×
Are you a member of the Splunk Community?
Sign in or Register with your Splunk account to get your questions answered, access valuable resources and connect with experts!
- Find Answers
- :
- Splunk Platform
- :
- Splunk AppDynamics
- :
- Re: Memory usage for Windows machine agent and dat...
Options
- 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
Thierry_QUESSAD
Engager
03-13-2020
06:26 AM
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
1 Solution
- Mark as New
- Bookmark Message
- Subscribe to Message
- Mute Message
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Thierry_QUESSAD
Engager
04-01-2020
10:27 PM
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
Allan_Schiebold
Communicator
03-17-2020
10:40 AM
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
Florian_CRISTIN
Engager
03-19-2020
01:05 AM
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
Thierry_QUESSAD
Engager
04-01-2020
10:27 PM
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.
Get Updates on the Splunk Community!
Why You Can't Miss .conf25: Unleashing the Power of Agentic AI with Splunk & Cisco
The Defining Technology Movement of Our Lifetime
The advent of agentic AI is arguably the defining technology ...
Deep Dive into Federated Analytics: Unlocking the Full Power of Your Security Data
In today’s complex digital landscape, security teams face increasing pressure to protect sprawling data across ...
Your summer travels continue with new course releases
Summer in the Northern hemisphere is in full swing, and is often a time to travel and explore. If your summer ...
