Fully featured low overhead profiler for Java EE and Java SE platforms.
Easy-to-use performance and memory .NET profiler for Windows, Linux and macOS.
Secure and easy profiling in cloud, containers and clustered environments.
Performance monitoring and profiling of Jenkins, Bamboo, TeamCity, Gradle, Maven, Ant and JUnit.

Connect to profiled application

Once the profiled application is running, you should connect to it to obtain and analyze profiling results.

All detected .NET applications are shown in the "Monitor Applications" list on Welcome screen. Connect to the application you want to profile by clicking on its name.

The colored circle indicates the profiler agent status in the CLR process. Green circle means the agent has been loaded, and connection will happen immediately. Orange circle means the agent has not been loaded yet, and the profiler will automatically attach the agent before connection.

Local applications are shown under the node with local applications icon. Applications running on the remote machines are shown under their own nodes with remote connection icon. To add a new remote machine click add remote connection. See Profile remote applications to learn more.

Profiler hides development tools, such as IDEs, in the list by default. This can be configured by clicking on the filter icon.

If you do not see your application it the list, please read profiling troubleshooting.

Profiling session

After a connection is established successfully, the profiling session tab opens. It displays the profiled application telemetry, and provides the toolbar to control profiling.

Profiler toolbar
Toolbar Button Description
Capture performance snapshot - save the profiling results to a file, for comprehensive analysis
CPU profiling controls
Start thread state profiling Stop thread state profiling Thread stack telemetry control
Capture memory snapshot
Object allocation recording controls
Force garbage collection in the profiled application
Start exception profiling Stop exception profiling Reset recorded exception data Exception profiling controls
trigger Triggers - configure actions automatically performed on events
Clear telemetry charts Clear all telemetry charts
Pause the telemetry update Pause - stop/start receiving data from profiled application
Refresh telemetry data Refresh - immediately receive profiling data from the profiled application and update the views
Transfer snapshots during remote profiling

You can close the profiling session tab by using File | Close Profiling Session.

You can connect to and disconnect from the profiled application as many times as you wish during its run time.

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.