Analyze Performance: Basic Options

Use to configure basic and advanced options for the profiling session. The following basic options are available for analyzing the object lifecycle. If you are configuring a custom configuration, click Advanced Settings to specify advanced options. ?

Element Description

Quick

Samples the application and takes a stack trace periodically. This option is less precise than instrumenting methods, but the overhead is lower. This option can help you locate methods that you might want to instrument.

Advanced

Instruments all of the methods of the profiled application if you do not specify any root methods.

When entering a method, threads generate a "method entry" event. Threads generate a corresponding "method exit" event when exiting the method. The timestamps for both of these events are recorded. This data is processed in real time.

You can limit the part of the application's code that is instrumented by defining root methods. This option can greatly reduce the profiling overhead. Specify a root method using the context menu in the source code or by clicking customize to open the Edit Profiling Roots dialog box. When you specify a root method, profiling data is not collected until one of the application's threads enters the root method.

Filter

Sets a filter to limit the classes that are profiled and control the overhead. The following default filters are available.

  • Profile all classes
  • Profile only project classes
  • Profile project and subprojects classes
  • Quick filter
  • Exclude Java Core Classes

If you select Profile Only Project Classes or Profile Project and Subprojects Classes, click Show Filter Value to see the classes that are to be profiled.

If you select Quick Filter, click Edit Filter Value to see and modify the filter criteria.

ClickEdit Filter Sets to create your own filter.

Profile project and subprojects classes is only available if the project contains subprojects.

Use Defined Profiling Points.

When selected, any actions that are initiated by enabled profiling points in the project are performed. Disabled profiling points are ignored. When deselected, all profiling points in the project are ignored.


The Overhead bar graph provides you with a rough indication of the overhead that are incurred when you profile the application with the current settings.


Related Topics

Developing Applications with NetBeans IDE,

Developing Applications with NetBeans IDE,

Developing Applications with NetBeans IDE,

Copyright © 2014, Oracle and/or its affiliates. All rights reserved.