Call Tree shows method execution paths. Each method node in the tree represents a top-level method executed by a certain thread. The method node lists methods it called and metrics collected during profiling.
- Get a quick overview on application activity.
- Examine execution path of slowest methods (the ones that consume most time or are called frequently).
- Determine critical execution paths.
- Apply filter by method to limit other filters with time intervals where only the method you are interested in was executed.
The percentage of time spent in a call relative to the total selected time.
Short method name.
Total time spent in a call and its subtree. See details below.
Full method name.
How Call Time Is Calculated
UserMethod1 = A + B + C + D + E + F + G + H + I
|UserMethod2 = B + D
| |SystemMethod2 = D
|SystemMethod1 = C + E + F + G + H + I
|SystemMethod2 = E
|SystemMethod1 = F + H
| |UserMethod1 = H
|UserMethod2 = G + I
|SystemMethod1 = I
Scoping to Particular Method Calls
To scope to a particular method call:
After you open a particular method call, it becomes a root node in Call Tree. All other calls except the subtree of the selected node are hidden. This also automatically applies a filter by the selected method occurrence. See details about filtering next in this section.
If a method was called from a number of places, you can merge all method call occurrences within one page.
To merge and show all method calls occurrences:
After this, the selected method becomes the root node in Call Tree containing all the occurrences. All other calls are hidden. This also automatically applies a filter by the method occurrences and their subtrees.
To return back to the previous call tree root, click the back button at the top.
Back Traces View Mode
How Call Tree Works as a Filter
After the filter is applied, other filters will show data only for the time intervals where the selected method occurrence(s) (including subtree) was executed.