When analyzing application performance, you can choose to limit the source code that is instrumented by
specifying a root method. When you profile an application by instrumenting a root method, profiling data
is collected when one of the application's threads enters and leaves the root method.
The advanced Edit Profiling Roots dialog box provides more advanced options
for adding, editing and removing the root methods that are specified
in the Edit Profiling Roots dialog box.
You open this dialog box by clicking Advanced in the Edit Profiling Roots dialog box.
The dialog box lists the profiling root methods that will be instrumented
when you analyze the application performance.
You can perform the following tasks in the dialog.
To define the profiling root you need to specify the following details.
Add. Click Add to specify a class and method that you want to instrument.
Edit. Select a root method and click Edit to modify the selected class and method.
Remove. Select a root method and click Remove to remove the method from the list
of methods that are instrumented.
Notes:
You may need to first mount the file system or a JAR file that contains your root
method's class, e.g. if this class does not belong to your application's
classpath. That is the case, for example, when profiling code running on
top of a Web/Java EE server.
If you choose a given method as a root when a thread is already
executing it, profiling will not start. To begin profiling, a "fresh" call
to the root method is required.
Once partial application profiling is initiated, profiling data
is not collected until one of the application's threads enters the profiling root method.