Who is this for?

This is an introductory topic for developers who want to analyze the performance of Java applications on Arm Neoverse-based servers using flame graphs.

What will you learn?

After completing this Learning Path, you'll be able to perform the following tasks:

  • Set up a benchmarking environment using Tomcat and wrk2.
  • Generate flame graphs using async-profiler.
  • Generate flame graphs using a Java agent.

Prerequisites

Before starting, you'll need the following prerequisites:

  • Access to both Arm-based and x86-based computers running Ubuntu, or cloud-based server instances
  • Basic familiarity with Java applications and performance profiling using flame graphs

Summary

AI-assisted

This summary was 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.

Close
?
You’ll profile a Java HTTP workload on an Arm Neoverse server by applying repeatable load with Tomcat and wrk2. First, you’ll capture CPU samples with async-profiler and generate a flame graph. Then, you’ll profile with a Java Virtual Machine Tool Interface (JVMTI) agent and the FlameGraph toolkit. You’ll compare both views to identify the methods and call stacks that dominate execution under load.
Next