Profiler - Custom Configurations

Home > Profiling Tasks > Custom Profiling

Editing and Creating Custom Profiling Configurations

The Custom Profiling box appears when you choose to edit or create a configuration through the Run Custom Profiling task. This box allows you to further refine the profiling parameters for the different modes. These modes are the same general profiling modes that are available as predefined commands. The paramaters available depend on which of the following profiling modes you choose.

When working with a custom configuration, you can click Override Global Settings to override the settings defined in Profiler Options dialog . This will modify the settings for the configuration.

Custom Profiling

CPU Profiling

The basic choice between profiling the entire application, part of the application, or the code fragment is the same as in the Analyze Performance command, with the addition of the following profiling options:

  • Method: full or sampled
  • Timers: absolute, thread CPU or both
  • Maximum number of profiled threads
  • Instrumentation: filter
  • Instrumentation: scheme
  • Instrument/not instrument various special Java methods

For more about these settings, see CPU Profiling settings.

Memory Profiling

The basic choice between recording only object creation and the entire object lifecycle is the same as in the Analyze Memory Usage command. Additionally, the following options are available:

  • Stack sampling depth: full or limited
  • Take stack sampling every... (stack sampling interval)
  • Run garbage collection when getting memory results

For more about these settings, see Custom Memory Profiling settings.


Monitoring mode has no options and works exactly the same way as the Monitor Application command.

Optional settings

Independent of the mode selected, the following options allow you to further control the profiling process and the results:

  • Enable Thread Monitoring

    When selected, system and application threads activity is monitored from application startup. For more about these settings, see Thread Monitoring.

  • Override Global Settings

    For each configuration, you can modify the Profiler Options in the Global Settings for Configuration dialog box. The dialog box enables you to modify the following settings:

    • Working Directory

      Specify the directory that will become current for your application when it starts. For example, you may need to specify a specific working directory when attaching Profiler to a running JVM.

    • Java Platform

      The Java Platform combo box enables you to specify the target JVM to use when profiling your application. The default JVM is the JVM the IDE is running on. The combo box lists the available Java platforms. To add or remove a platform, choose Tools > Java Platform Manager from the main menu.

    • JVM Arguments

      Specify any arguments to pass on to the JVM, for example, the default maximum heap size.

    Override Global Settings

See also


Project Features

About this Project

Profiler was started in November 2009, is owned by Tomas Hurka, and has 62 members.
By use of this website, you agree to the NetBeans Policies and Terms of Use (revision 20160708.bf2ac18). © 2014, Oracle Corporation and/or its affiliates. Sponsored by Oracle logo
Please Confirm