## Calibrating the Profiler

See Also

You need to calibrate the IDE before you can use the IDE to profile an application. You need to run the calibration process for each JDK you will use for profiling. You do this because instrumenting the bytecode of the application imposes some overhead, and the time spent in code instrumentation needs to be "factored out" in order to achieve more accurate results.

To calibrate the IDE to the local system:

1. Close any other programs that are running.
   - The IDE will run the calibration if other applications are running, but running any CPU-intensive programs when performing the calibration may affect the accuracy of profiling results.
2. Choose Profile > Advanced > Run Profiler Calibration from the main menu.
3. Choose the Java Platform that will be used for profiling and click OK.

When you click OK, the IDE will collect calibration data on the selected Java platform. When the calibration process is complete you can start using the IDE to profile your applications.

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

To calibrate the IDE to a remote system:
To calibrate the IDE to a remote system, see the following NetBeans FAQ:

### Calibrating the system again

You only need to calibrate the IDE once for each JDK you will use. However, you should run the calibration process again when anything changes on your local or remote configuration that could affect system performance. The following could affect system performance:

- Any hardware upgrade
- Any significant change or upgrade of the operating system
- An upgrade of the Java platform used for profiling

See Also
  Selecting a Profiling Task

Legal Notices