All methods of profiled packages are shown in the call tree. Start the filter list with this
type to profile selected packages only.
The first call from a profiled class into a compact class is shown in the call tree,
but further calls into compact classes are not measured separately. If the first filter is compact, no classes
are profiled by default.
Ignored packages or classes are not profiled at all. If the first filter is ignored, all other
classes are profiled by default.
com.mycorp. packages, and if your class com.mycorp.MyClass calls a method in
java core classes, all those calls will be measured, but their internal call structure will not be resolved.
In the call tree view, such method calls are opaque
and will be labeled with a red corner.
Package filters include all sub-packages. For example, if you have one profiled package filter with the name
com.mycorp., it includes all classes directly in the com.mycorp. package
as well as the com.mycorp.test and the com.mycorp.test.detail packages.
Filter rules are evaluated from top to bottom, the last matching rule is applied.
For example, if you add an "compact" filter for the com.mycorp. packages, but further down
add an profiled package filter for the com.mycorp.test package, the com.mycorp.test package
is profiled while other classes in the com.mycorp. packages are not.
[Add] button, you
also get the option to select filters in a package browser. The package browser shows packages for
If, at any later point, you wish to restore these default exludes, you can use the
reset filters to default button on the right side.
All current filter settings will be lost in that case.
save button, the
open button lets you replace the current filter configuration with
a filter template.
On the session defaults tab of the general settings dialog you can change the default filter template used for new sessions.