Not a customer? Click the 'Start a free trial' link to begin a 30-day SaaS trial of our product and to join our community.
Existing Cisco AppDynamics customers should click the 'Sign In' button to authenticate to access the community
03-13-2020 06:26 AM - last edited on 03-13-2020 08:30 AM by Ryan.Paredez
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
Solved! Go to Solution.
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.
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.
04-01-2020 10:27 PM - last edited on 04-02-2020 09:11 AM by Ryan.Paredez
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.
User | Count |
---|---|
3 | |
2 | |
2 | |
1 | |
1 | |
1 |
Thank you! Your submission has been received!
Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form