|
The allocation hot spots view shows a list of methods where objects of a selected class
have been allocated. Only methods which contribute at least 0.1%
of the total number of allocations are included. The methods are filtered according to the
filter settings. This view
is similar to the
hot spots view in JProfiler's
CPU section except that it shows allocations
of class instances and arrays instead of time measurements.
Note: The notion of a hot spot is relative. Hot spots depend on the filter sets that you have enabled in the filter settings. Filtered methods are opaque, in the sense that they include allocations performed in calls into other filtered methods. If you change your filter sets you're likely to get different hot spots since you are changing your point of view. Please see the help topic on hot spots and filters for a detailed discussion.
In order to prepare allocation hot spots, you have to click on the
Before the allocation hot spots are calculated, the allocation options dialog is shown. The class or package selection as well as the selected liveness mode are displayed at the top of the allocation call tree view. |
The hot spot calculation options can be selected in the drop-down list above the table labeled
"Hot spot options". The allocated memory calculation section lets you calculate hot spots from
By setting a view filter, you can analyze hot spots in selected packages. The cutoff will then be calculated relative to the set of filtered classes. In that way, hot spots may be shown that are otherwise below the cutoff threshold. Note: The notion of a method hot spot is relative. Method hot spots depend on the filter sets that you have enabled in the filter settings. Filtered methods are opaque, in the sense that calls into other filtered methods are attributed to their own allocated memory. 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 hot spots and filters for a detailed discussion. |
Every hot spot is described in several columns:
If you click on the
|
JProfiler automatically detects Java EE components
and displays the relevant nodes in the hot spot backtraces tree with special icons that depend
on the Java EE component type:
servlets JSPs EJBsFor certain classes, JProfiler shows a display name:
special icon and the prefix
HTTP:, followed by the part of the request URL on which the hot spot backtraces tree
was split. Note that HTTP nodes group request by the displayed URL.
|
The allocation hot spots view has an aggregation level selector. It allows you
to switch between
The hot spot backtraces tree doesn't display all method calls in the JVM, it only displays
|
|
When navigating through the hot spot backtraces tree by opening
method calls, JProfiler automatically expands methods which are only called
by one other method themselves.
To quickly expand larger portions
of the hot spot backtraces tree, select a method and choose
If you want to
collapse an opened part of the hot spot backtraces tree, select the
topmost method that should remain visible and choose
|
If a method node is selected, the context menu allows you to quickly add a
method trigger for the selected method with the
add method trigger action.
A dialog will be displayed where you
can choose whether to add the method interception to an existing method trigger or whether to create a
new method trigger.
|
Nodes in the hot spot backtraces tree can be hidden by selecting them and hitting the 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 |
|
For method, class or package nodes, the context menu and the View menu have an
Add Filter From Selection entry. The sub-menu contains actions to add
appropriate filters as well
as an action to add an ignored method entry.
If a node is excluded, you will get options to add a profiled package, otherwise you will get options to add a compact or ignored filter. These actions are not available for classes in the "java." packages. |
By marking the current state, you can follow the evolution of the allocation hot spots.
This is particularly useful for quickly finding the origin of memory leaks.
Marking the current values can be achieved by
By default, the difference column is sorted on the absolute values in it, this can be changed in the allocation hot spots view settings dialog. You can remove the mark by
|
If garbage collected objects are shown, you can reset the accumulated data
by clicking on the
reset action in the toolbar or choosing the the
Reset Garbage Collector History menu item
in the View or context menu. All garbage collector data will be
cleared and the view will be empty for the "Garbage collected objects" mode until
further objects are garbage collected and a new allocation call tree or allocation hot spots are
calculated. Note that you can force garbage collection by clicking on the garbage collector
tool bar button or by
selecting Profiler->Run Garbage Collector from
JProfiler's main menu.
|
| Only recorded objects will be displayed in the allocation hot spots view. See the memory section overview for further details on allocation call stack recording. |
The View->Take Heap Snapshot For Selection menu item and the
corresponding
toolbar entry take a new snapshot, switch to the
heap walker view and create an object set with
the currently selected class and allocation hot spot.
|