Read the profiling report
In the Profiler tool window, the collected data is presented on several tabs: Flame Graph, Call Tree, Method List, and Events (for JFR). The left-hand part of the tool window lists application threads. By clicking on each thread you can go in more details.
Navigate the report
The Profiler tool window allows you to jump between the tabs while staying focused on a specific method. Right-click the necessary method and select another view in which you want to open it.
If you want to review a method in the editor, right-click it on any tab and select Jump to Source or press F4.
Export profiling results
On the left frame of the Profiler tool window ( ), click .
In the dialog that opens, name the file, specify the folder in which you want to save it, and click Save.
Import profiling results
You can import profiling data to the IDE to analyze it using the profiling tools. Make sure that the files that you import were created by Async Profiler or have the .jfr format.
From the main menu, select.
Select the file that you want to import and click Open.
The flame graph visualizes the application call tree with the rectangles that stand for frames of the call stack, ordered by width. Methods that consume more CPU time and memory resources are wider than the others.
The blue color of the blocks stands for native calls, yellow stands for Java calls.
When you read the flame graph, focus on the widest blocks. These blocks are the methods that are presented in the profile most. You can start from the bottom and move up, following the code flow from parent to child methods, or use the opposite direction to explore the top blocks that show the functions running directly on the CPU. In this case, you can use theoption change the graph view.
Flame Graph layout
Each block represents a function in the stack (a stack frame). The width of each block corresponds to the method’s CPU time or memory used (or the allocation size, in case of allocation profiling).
On the Y-axis, there is a stack depth going from bottom up. The X-axis shows the stack profile sorted from the most resource-consuming functions to the least consuming ones.
Show details in tooltips
Hover the mouse pointer over a block to display a tooltip.
The tooltips show the fully qualified method name, the percentage of the parent sample time, and the percentage of total sample time.
Zoom the graph
Use the and options to zoom the graph.
To focus on a specific method, double-click the corresponding block on the graph.
To restore the original size of the graph, click 1:1.
Search the graph
If you want to locate a specific method on the graph, start typing its name. The graph highlights all blocks with method names matching your search request.
The Call Tree tab represents information about a program’s call stacks that were sampled during profiling. The top-level All threads merged option shows all threads merged together into single tree. There's also a top-down call tree for each thread.
For each method, the tab shows the following information:
The method name
Percentage of total sample time or parent's sample time
The total sample count
- Recursive calls
- Filtered calls
Filter Call Tree results
The Call Tree tab allows you to collapse the frames you are not interested in at the moment by applying filters. For example, you can hide library classes or the classes that come from specific frameworks to be able to focus on the application itself.
The blue arrow hyperlink right after the percentage presents a filtered sequence of calls. Click it to expand this sequence.
Configure filtering rules
In this dialog, you can modify the existing rules and add new ones.
Configure the packages or specific classes that you want to be able to hide in the output.
To filter all methods in a class, specify the fully qualified class name (for example:
To filter specific methods in a class, use the following format: fully qualified class name: method name (for example:
* : myMethod()).
Apply the changes and close the dialog.
Collapse recursive calls
A complex application that has multiple recursive methods may be very difficult to analyze. In a regular Call Tree view, recursive calls are displayed as they are called – one after another, which in case of complex call stacks with multiple recursive calls leads to almost infinite stack scrolling.
IntelliJ IDEA detects a recursion when the same method is called higher up in the call stack. In this case, the subtree is taken out of the call tree and then attached back to the first invocation of that method. This way you can bypass recursion and focus on methods that consume most of the resources and calls that they make.
Collapsing recursive calls allows you to see the total amount of time spent in these calls as if there was no recursion.
Folded recursive calls are marked with the icon on the Call Tree tab. Click it to open the recursive call tree in a separate tab. You can preview the number of merged stacks in a tooltip.
What-if: focus on specific methods
IntelliJ IDEA allows you to examine specific methods in the Call Tree: you can exclude particular methods or other way around, focus only on the methods in which you are interested at the moment.
Right-click the necessary method on the Call Tree tab and select one of the following options to open the results in a dedicated tab:
Focus on Subtree: show only the selected method call. Parent method sample time counter shows only the time spent in the selected subtree.
Focus on Call: show the selected method and the methods that call it. When this option is enabled, every time frame shows only the time spent in the selected method.
Exclude Subtree: ignore the selected method call.
Exclude Call: ignore all calls to the selected method.
The Method List collects all methods in the profiled data and sorts them by cumulative sample time. Every item in this list has several views:
Back Traces shows the hierarchy of callers. Use this view to trace which methods call the selected method.
Merge Callees tries to summarize all methods that are called by the selected one.
Callees List shows all methods that were called from the selected one.
Java Flight Recorder Events
Java Flight Recorder collects data about events. Events occur in the JVM at a specific point in time. Each has a name, a timestamp, and an optional payload.