Analyze Java performance on Arm servers using flame graphs
Introduction
Set up Tomcat benchmark environment
Generate Java flame graphs using async-profiler
Generate Java flame graphs using a Java agent
Next Steps
Analyze Java performance on Arm servers using flame graphs
Review frequently asked questions
These FAQs were drafted with an approved AI-assisted workflow and reviewed by Arm contributors before publication. Human technical review remains part of the process so the final page reflects engineering rigor, accuracy, and Arm editorial standards.
Profile the Tomcat process. Use your system’s process listing to find the PID, and start profiling while
wrk2 is actively generating load.Yes. Install and run
async-profiler on the same Arm-based Linux machine where Tomcat is running to ensure accurate profiling.Run
wrk2 from an x86_64 Ubuntu client so that it sends HTTP requests to the Tomcat server that you’re profiling. Confirm that you can reach the Tomcat endpoint before starting the benchmark.Check that the profile output shows Java method names rather than raw memory addresses. If the output doesn’t, verify that
libperf-jvmti.so is present and loaded by the JVM.Open
profile.svg in a browser to analyze the sampled profiling result from the benchmark. Expect a visualization of sampled stacks during the benchmark. The widest stacks indicate where time is spent, so that you can focus on the hottest Java methods and code paths.