Calibrating NetBeans Profiler

Calibrating NetBeans Profiler

Instrumenting the bytecode of the profiled application imposes some overhead. To guarantee the high accuracy of profiling results, NetBeans Profiler needs to collect calibration data in order to "factor out" the time spent in code instrumentation. You need to run the calibration process for each JDK you will use for profiling. The calibration data for each JDK is saved in the .nbprofile directory in your home directory.

You are prompted to run the calibration the first time you invoke NetBeans Profiler. You are also prompted if the calibration data for the local machine and JVM is unavailable.

Running the Calibration

When performing calibration, make sure that no other programs are running on the same machine (or at least that no other program is performing any significant computation at the time). Profiler will run the calibration regardless, but running any CPU-intensive programs when performing the calibration may affect the accuracy of profiling results.

Warning: If you are profiling on a computer that has a processor with dynamic CPU frequency switching feature (like SpeedStep or PowerNow on modern notebooks), ensure that this is disabled when running the calibration and that the calibration is run at the same CPU frequency as when profiling.

There are two scenarios for running calibration:

  • Calibration for local profiling. To collect calibration data for profiling on your local system, choose Profile > Advanced Commands > Run Profiler Calibration from the main menu. The following dialog is displayed:

    Select Java Platform dialog box

    Choose the Java Platform that will be used for profiling and click OK. A dialog box appears when the calibration process is finished. You can then start to profile your application locally.

  • Calibration for remote profiling. To collect calibration data on a remote system for profiling remotely, download the Profiler server bundle for the appropriate platform at and unzip the archive on the remote machine. To calibrate, run the calibrate.bat/ script placed in the bin directory. When calibration is complete, the results of the calibration are displayed in the console. You can then start to profile your remote application.

    screenshot of console

Rerunning the Calibration

You should rerun the calibration when anything changes on your local/remote configuration that could affect system performance, such as the following:

  • Any hardware upgrade
  • Any significant change/upgrade of the operating system
  • An upgrade of the Java platform used for profiling

You should never share calibration data between various computers or systems.

See also



Project Features

About this Project

Profiler was started in November 2009, is owned by Tomas Hurka, and has 61 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