This document contains the results of tests done to measure resource memory consumption by the Microservices Profile.Summary
Provides a configuration that has a foot print of less than 5 MB Heap compared to Tomcat Typical of around 12 MB Heap. This uses the CA APM Tomcat Agent installation. This configuration disables SQL and JMX metrics, setups up BA to be enabled via container parameters and increases Transaction Trace visibility. This configuration is for APM 10.3, but could be applied to other versions of APM as well. Goal: To find optimized settings of APM agent to reduce resources below 5 MB Heap.Test #1
When: 2016 December
What: APM 10.1
Who: Abi Mohan
Tomcat Java Agent testing
<Please see attached file for image>Test #2
Who: Kondichetty Joel, Anil K <[email protected]
What: APM 10.7 sp1
Overall Summary :
· The dumps specify that CA APM is the second largest consumer of heap (16%) whereas 24% is consumed by their internal application class loaders which is the highest consumer of heap.
· The heap consumption by APM over a period appears to be stable.
· There are no leaks observed.
· The size of the cache signifies object checkout and check-ins as expected and according to design.
· Overhead across the dumps averages to 16.5% of the total heap whereas our findings in our lab with OOB settings according to the below report is around 34%.
Table that include both profiles (SI = high, SI = low) For the microservices profile SI=low has little improvement over SI = high.
<Please see attached file for image>