Revision as of 10:39, 22 December 2011 by Thurka (Talk | contribs)
(diff) ← Older revision | Current revision (diff) | Newer revision → (diff)

How do I run the calibration process on a remote machine?

To collect calibration data on a remote system for profiling remotely, do the following:

  1. Create Profiler Remote Pack in Attach wizard (if you are running NetBeans 6.1 or older, download the Profiler Remote Pack for the appropriate platform at http://profiler.netbeans.org/) and unzip the archive on the remote machine.
  2. Run the calibrate.bat/calibrate.sh script located in the bin directory.

When the calibration is finished, the results of the calibration are displayed in the console. You can then start to profile your remote application.

What exactly does the Profiler Calibration mean?

When instrumenting bytecode and obtaining time stamps from the OS, extra overhead is imposed in the profiled application. During calibration this extra time is measured and then subtracted from collected results during profiling.

In fact the JDK which will run the profiled application is being instrumented, not the IDE itself. Note that if your computer uses a dynamic frequency switching feature (Like SpeedStep or PowerNow!), you have to disable it before calibration and during profiling, otherwise collected data won't be accurate.

The calibration data for each JDK is saved in the .nbprofile directory in your home directory.

Back to NetBeans IDE Profiling FAQs

Back to NetBeans User FAQs

Not logged in. Log in, Register

By use of this website, you agree to the NetBeans Policies and Terms of Use. © 2012, Oracle Corporation and/or its affiliates. Sponsored by Oracle logo