Is there any upper threshold for the number of metrics an agent can collect ?
I see an issue with one of my collectors which has 90% java memory utilized all the time, I'm wondering if I am collecting far too many metrics than recommended.
Any thoughts around this would be extremely helpful, Thank you.
EMs should be set to reserve the entire heap that it is configured for, meaning the min/max setting should be the same for performance reasons.
Expanding and contracting the heap is inefficient for tools such as APM and its better for it to grab it all at initialization.
Now, if you have followed best practices and set the heap properly, and you're still seeing utilization over 75%, then there's a problem.
Thanks Davis, I don't have any other processes sharing the EM's heap, so I believe that I'm good in that regard.
My question back to you is, how am I supposed to recognize that my heap is smaller for the number of metrics and agents in my cluster ?
Is there a formula to derive that equations?
Check out the Sizing and Performance Guide in the wiki. It will help you with that.
Yes, it did help, Thank you.
For anyone who is looking for the link:
CA APM Sizing Recommendations - CA Application Performance Management - 10.5 - CA Technologies Documentation
If the future, I may post an update blog about sizing best practices. We did a session as CA World last year about this and we'll soon have some updated numbers to provide concerning G1GC and APM 10.7.
That sounds interesting, Thank you
Also, what version of APM are you using?
APM Team Center