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.

Manually enable profiling of local applications

The following describes how to manually enable profiling of local applications.

Note that in most cases, it is profile local applications using the profiler UI. Should you need to profile remote applications, read here.

1. Make sure the profiler is installed

The profiler installer not only creates necessary files, but also registers the profiler agent DLL.

2. Set up a profiling environment

Specify the following two environment variables:

Variable Value

To profile services modify system variables, not user variables.

GUID is unique for each profiler version and build. Please find its value in <Profiler Installation Directory>\guid.txt
Pay attention that GUID starts with { and ends with }

You may need to restart Windows. For detail, please refer to the following MSDN article

Special notes on profiling a Windows service can be found here.

3. Run the application

If profiling was properly enabled, the profiled application should start with the profiler agent.

To ensure it has started with the profiler, check whether log file has been created:
<user home>\.ynp\log\<session name>-<PID>.log

4. Connect to the application

The profiled application should appear on the Welcome screen of the profiler. If it does not, please refer to Local profiling troubleshooting.

Connect to the profiled application to obtain profiling results.