Probe Hot Spots | ![]() ![]() ![]() |
![]() |
The hot spots view is conceptually similar to the CPU hot spots view.
Instead of showing method hot spots, it shows payload names published by the selected probe. Payload names
(such as the SQL string of a statement for the JDBC probe) have an associated duration, and the ones that take the
most time result as the top hot spots.
Payloads are also connected with particular call stacks, so the hot spots view can show a merged tree of back traces. Even if sampling is enabled, JProfiler records the exact call traces for probe payloads by default. If you want to avoid this overhead, you can switch it off in the profiling settings. For more information on the payload concept, please see the corresponding help topic |
![]() |
Every hot spot is described in several columns:
|
![]() |
If you click on the ![]()
|
![]() |
For certain probes, such as the "JPA/Hibernate" probe, the top-level elements in the backtraces are
![]() ![]() ![]() ![]() The back traces below a "deferred operations" node are not directly associated with the actual execution of the hot spot. They show
|
![]() | In the view filter at the bottom of the tree you can enter the full name of a payload or only a part of it. Only payloads whose names begin with this fragment are displayed. You can also use wildcards ("*" and "?") to select groups of payloads. Please note that if you use wildcards, you have to manually append a trailing "*" if desired. You can display the union of multiple filters at the same time by separating multiple filter expressions with commas, e.g. test-, MyTest-*-123. |
![]() |
The ![]() |
![]() ![]() ![]() |