The Java Agent typically adds between 0% to 2% additional CPU consumption.

However, certain factors can increase CPU overhead from the agent beyond 2%. These include the use of resource-intensive Splunk AppDynamics features, such as asynchronous transaction tracking. Very active environments or configuration settings that result in a high number of metrics or snapshots reported per minute can also affect agent resource consumption.

In all cases, Splunk AppDynamics recommends that you test the agent in a staging environment, and monitor resource consumption of your application to ensure that it remains within proper operating parameters.

If your application operates within a small margin of its existing memory resource allocation, you may choose to increase the allocation for the application. Splunk AppDynamics recommends allocating the following amounts of additional Heap and PermGen space to accommodate the agent:

• Maximum heap size (-Xmx): 100 MB in addition to the amount required by the application
• Maximum PermGen (permanent generation) heap size (-XX:MaxPermSize): 20 MB in addition to the amount required by the application. The setting for MaxPermSize is applicable only for Java 6 or Java 7.
• For network bandwidth consumption, see App Agent Network Bandwidth Usage.