Splunk AppDynamics

Memory usage for Windows machine agent and database agent

Thierry_QUESSAD
Engager

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

Labels (1)
0 Karma
1 Solution

Thierry_QUESSAD
Engager

Hello,

I opened a case to the support and the requirements of memory for these agents are huge.

https://docs.appdynamics.com/display/PRO45/Standalone+Machine+Agent+Requirements+and+Supported+Envir...

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.

View solution in original post

0 Karma

Allan_Schiebold
Communicator

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. 

0 Karma

Florian_CRISTIN
Engager

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.

Thierry_QUESSAD
Engager

Hello,

I opened a case to the support and the requirements of memory for these agents are huge.

https://docs.appdynamics.com/display/PRO45/Standalone+Machine+Agent+Requirements+and+Supported+Envir...

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.

0 Karma
Get Updates on the Splunk Community!

.conf25 Registration is OPEN!

Ready. Set. Splunk! Your favorite Splunk user event is back and better than ever. Get ready for more technical ...

Detecting Cross-Channel Fraud with Splunk

This article is the final installment in our three-part series exploring fraud detection techniques using ...

Splunk at Cisco Live 2025: Learning, Innovation, and a Little Bit of Mr. Brightside

Pack your bags (and maybe your dancing shoes)—Cisco Live is heading to San Diego, June 8–12, 2025, and Splunk ...