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

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 icon. Applications running on the remote machines are shown under their own nodes with icon. To add a new remote machine click . 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 Local profiling troubleshooting for local applications and Remote profiling troubleshooting for remote applications.

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.

Toolbar Button Description
Capture performance snapshot - save the profiling results to a file, for comprehensive analysis
CPU profiling controls
Thread stack telemetry control
Capture memory snapshot
Start/stop object allocation recording
Triggers - configure actions automatically performed on events
Force garbage collection in the profiled application
Exception telemetry controls
Clear all telemetry charts
"Pause" - stop/start receiving data from profiled application;
"Refresh" - immediately receive profiling data from the profiled application and update the views

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

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