Agent Heap and CPU Issues
search cancel

Agent Heap and CPU Issues

book

Article ID: 395037

calendar_today

Updated On:

Products

DX SaaS

Issue/Introduction

 

1) Agent High CPU/Heap issue -- com.wily.util.adt.ConcurrentWeakIdentityThreadLocalHashMap taking lot of JVM resources.

 

2) Agent Min/Max settings -- Confirm what is the Broadcom APM agent Min and Max JVM heap usage?

 

Resolution

1) General suggestions

Troubleshooting Agent Java Crashes

Also try disabling socketTracing if enabled . This produces high CPU.

  • Turn off tracers for network, filesystem, and System File Metrics in  
    toggles.PBD
     . They are not recommended to be enabled in Production.
    #TurnOn: SocketTracing
    #TurnOn: UDPTracing
    #TurnOn: FileSystemTracing
     

you want to temporarily disable autoprobe to see how  the server performs without the agent:

introscope.autoprobe.enable=true 

 

2) It will be one of these "it depends" answers.

This has a good section on agent sizing

Agent Sizing and Performance

If a high memory issue, you can explore this.

Agent Memory Overhead Property
Significant agent memory overhead only occurs in certain extreme cases. The typical trade-off for lowering memory consumption is a potential increase in response time. However, each application is unique and the trade-off between memory usage and response time can vary depending on each application.
introscope.agent.reduceAgentMemoryOverhead
This property specifies the agent configuration to use. Uncomment if you want to reduce the agent memory overhead. Values: true or false Default: false Example: introscope.agent.reduceAgentMemoryOverhead=false Notes:
This property is commented out by default.
Restart the managed application for changes to this property to take effect