Fully featured low overhead profiler for Java EE and Java SE platforms.
Easy to use performance and memory .NET profiler for Windows and Linux.
Performance monitoring and profiling of Jenkins, Bamboo, TeamCity, Gradle, Maven, Ant and JUnit.

Eclipse

Plugin installation

To enable integration, you should install the profiler plugin.

To install the plugin, run the profiler.

Use Profile from within IDE... action on Welcome screen or in "Tools" menu, select "Eclipse" and follow the instructions.

The wizard will open these instructions in your browser. Please follow them to complete the plugin installation.


Profiling from Eclipse

After the plugin is installed, Profile actions appear in the toolbar ...


... in the main menu ...


... and in context menus.

Additional launch parameters can be configured with Run | Profile..., tab YourKit Java 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.

32-bit or 64-bit JRE selection

This topic is not applicable to macOS where the profiler agent a universal binary.

On a 64-bit machine, the Profile action must know whether the JVM for launching the profiled application is 32-bit or 64-bit, in order to supply appropriate profiler agent version.

By default, the plugin attempts to automatically detect the JVM kind by obtaining available information from Eclipse.

For particular run configurations this may happen that the automatic detection is not possible. In this case Profile will fail with an error like Error occurred during initialization of VM. Could not find agent library printed in the Eclipse console. In this case use the "32-bit or 64-bit JRE Selection" section to specify Java bitness explicitly.

Navigation action

While profiling, 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.

Use Tools | Open in IDE (F7) to 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.

YourKit uses cookies and other tracking technologies to improve your browsing experience on our website, to show you personalized content and targeted ads, to analyze our website traffic, and to understand where our visitors are coming from.

By browsing our website, you consent to our use of cookies and other tracking technologies in accordance with the Privacy Policy.