JVM Profiling Report

Why: There are many ways to configure the Java Virtual Machine (JVM) which is used by the Remedy Mid-Tier. There is no one correct way to configure a JVM. What works for one load profile may not be correct for another. Whilst running test the JVM can be profiled in order to obtain information related to garbage collection, thread usage, CPU usage by the JVM etc. This information can be valuable even if the system is performing as expected as this ‘good’ profile can be used in comparison with a second profile that would be undertaken should the system start to respond poorly. The comparison with ‘good’ profile data can quickly rule out areas of concern when hunting down root cause bottlenecks and is necessary should the JVM become a bottleneck in itself.

The JVM Profiling Report obtains a baseline profile of mid-tier performance during test execution, in order to ascertain baseline characteristics of the running JVM during testing scenarios. This data is also required in order to reveal any pre-existing anomalies or JVM configuration issues with the system under test.

Scope: Tests will be repeated with JVM profiling enabled, in order to obtain data which characterizes the JVM experience during testing. This data can be used as a starting point to quickly exclude or take into account any performance issues related to the JVM should the performance of the system deteriorate.

Outcome: Any obvious areas of concern with the running behavior of the JVM will be highlighted in a report. If the customer makes any configuration changes to the JVM, then tests should be re-run in order to prove the effectiveness of such changes. A report containing the runtime characteristics of the JVM for each bolt on test will be provided.

Find out how Scapa TPP can help your business perform better.

Request a demo Enquire Today