Analyze Performance: Advanced Options

Use to create a custom configuration and set more advanced profiling options.

Click Advanced Settings in the configuration pane for your custom configuration to set the advanced options. Click Basic Settings to set the configuration options in the Basic Options pane.

The options that are available in the Advanced Settings pane depend upon the options that you select in the Basic Settings pane. If you choose the Quick option in the Basic Settings pane, you see fewer options in the Advanced Settings pane.

Settings for Quick (Sampled) Option

Element Description

Settings

Frequency setting

    Sampling Frequency.

Specifies how often the application is sampled.

Threads

Thread options

    Enable Threads Monitoring.

Monitors application threads from application startup.

When deselected (default), thread monitoring does not begin until you click Threads in the Threads window.

    Sample Threads States

Periodically updates thread states.

This option is selected by default.


Settings for Advanced (Instrumented) Option

Element Description

Settings

Method and timing settings

    Methods Tracking

Injects a "method entry" call at the beginning of each profiled method and a "method exit" call before each return when tracking methods.

Choose the granularity of tracking by selecting one of the following options: Exact Call Tree and Timing or Exact Call Tree, Sampled Timing.

        Exact Call Tree and Timing

Calculates the time spent in the method as the difference between the timestamp that is generated for each "method entry" and corresponding "method exit".

        Exact Call Tree, Sampled Timing

Calculates the time spent in the method as the difference between the timestamp that is generated for the "method entry" and corresponding "method exit" that fall approximately at the end of each sampling interval.

You must specify a sampling interval.

For more about which option to choose, see the following NetBeans FAQ:

    Exclude time spent in Thread.sleep() and Object.wait()

Does not profile these methods.

    Profile underlying framework setup

Profiles the startup of the application's target JVM.

    Profile new Threads/Runnables

Instruments the code for any thread or runnable started after the application enters the root instrumentation method.

This option is selected by default when profiling the entire application.

    Limit number of profile threads.

When selected, every time a thread that has not been previously registered enters the instrumented code, this counter is decremented. When it reaches zero, registration of new threads is stopped. Profiling data is collected only for the registered threads.

To reset the counter to this value, choose Profile > Reset Collected Results from the main menu

For more about when to use these option, see the following NetBeans FAQ:

    Use thread CPU timer (Solaris only)

Profiles the time spent executing the specified thread.

For more about using timers, see the following NetBeans FAQ:

    Instrumentation Scheme

Uses an instrumentation scheme to limit the number of instrumented methods. (Usually, it is best if the number of instrumented methods and the number of methods actually called by the application when it is profiled are the same or very close.)

        Total

Use this scheme to profile application startup, or an entire application such as a short-running command line utility With this scheme, all methods in a class are instrumented as soon as the class is loaded.

This scheme is selected by default when profiling the entire application

        "Lazy"

Use this scheme to profile a long running application as it has a low instrumentation overhead. For instance, use to profile a subset of the application code (where, for example, just one or more servlets running on top of an application server). Results in the smallest number of methods being instrumented.

This scheme is selected by default when profiling part of an application.

        Eager

Use this scheme as a compromise between the Total and Lazy schemes. This scheme is not recommended for long-running applications.

For more about instrumentation schemes, see the following NetBeans FAQ:

    Instrument

Instruments Method.invoke(), Getter/setter methods, and empty methods. By default, these types of methods are not instrumented.

For more about instrumenting these methods, see the following NetBeans FAQ:

Threads

Thread options

    Enable Threads Monitoring

Monitors application threads from application startup.

When deselected (default), thread monitoring does not begin until you click Threads in the Threads window.

    Sample Threads States

Periodically updates thread states.

    Enable Lock Contention Monitoring

When selected, application threads are monitored for lock contentions.



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.