NetBeans versions from 7.0 to 8.0 are supported.
To enable integration, you should install the profiler plugin.
To install the plugin, run the profiler.
When you run the profiler for the first time or after updating to a newer profiler version,
you will be automatically prompted to install the plugin. Also, you can explicitly launch the plugin installation wizard
After the plugin is installed, Profile actions are added to the main toolbar ...
... and to context menu of the editor:
You can profile Java SE and Java EE applications and applets.
Additional launch parameters can be configured in NetBeans in
, section "YourKit Profiler":
The "Profile" action starts the profiled application, and connects to it in profiler UI (unless opposite behavior is configured). The output of the profiled application appears in console, same as for "Run" action.
When profiling applications, you usually need to browse the related source code to understand the performance problems at hands. After the problem is located, you edit the source code to fix it.
Instead of forcing you to tell profiler where the source code of your application is located
and showing the code in feature-restricted custom-made "editor surrogate", YourKit provides an alternative approach.
When you have a method, class or field selected in the profiler UI,
to automatically open the underlying source code in the editor of your IDE - the best place to browse and edit code.
The navigation action works on the current selection and is available in both CPU and memory views. Take note of the extremely useful ability to locate the code of anonymous classes and their methods, which is a very difficult thing to do manually.