Depending on your selection of the aggregation level, the method hot spots will change. They and their hot spot backtraces will be aggregated into classes or packages or filtered for J2EE component types.
Note: The notion of a method hot spot is relative. Method hot spots depend on the filter sets that you have enabled on the method call recording tab of the profiling settings dialog. Filtered methods are opaque, in the sense that calls into other filtered methods are attributed to their own time. If you change your filter sets you're likely to get different method hot spots since you are changing your point of view. Please see the help topic on hotspots and filters for a detailed discussion.
Depending on your selection of the aggregation level, the hot spot backtraces can be aggregated into classes or packages. The J2EE-related hot spots themselves do not change for different aggregation levels.
For the J2EE related hot spot types, please see the help on the Java subsystems tab of the profiling settings for more information on how these calls are recorded.
If the method belongs to an unfiltered class, this time does not include calls into other methods. If the method belongs to a filtered class, this time includes calls into other filtered methods.
The hot spot list can be sorted on all columns.
If you click on the handle
on the left side of a hot spot, a tree of backtraces will be shown.
Every entry in the backtrace tree has textual information attached to it which depends
on the hot spot view settings.
Note: This is not the number of invocations of this method.
Note that the line number shows the line number of the invocation and not of the method itself.
If URL splitting is enabled,
each request URL creates a new node with a
special icon and the prefix
URL:, followed by the part of the request URL on which the hot spot backtraces tree
was split. Note that URL nodes group request by the displayed URL.
You can disable both J2EE component detection as well as URL splitting on the Java Subsystems tab of the profiling settings. Also, the URL splitting method can be customized in the profiling settings or with a custom handler in the profiling API.
When you switch between two aggregation levels, JProfiler will make the best effort to preserve your current selection. When switching to a a more detailed aggregation level, there may not be a unique mapping and the first hit in the hot spot backtraces tree is chosen.
The hot spot backtraces tree doesn't display all method calls in the JVM, it only displays
Runnable.run()
and the main method are always displayed, regardless of
the filter settings.
DEL
key
or by choosing Hide Selected from the context menu. Percentages will be corrected accordingly as if the
hidden node did not exist.
When you hide a node, the toolbar and the context menu will get a Show Hidden
action. Invoking this action will bring up a dialog where you can select hidden elements to be shown again.