Profile applications

1. On the toolbar, select the run configuration you want to profile.

2. In the menu Run | Switch Profiling Configuration choose a profiling configuration:

   • either one of the predefined configurations: Memory (Sampled allocations), Memory (Full allocations).

   • or your own custom configuration.

   

   Once the profiling is started, you will see the dotMemory Profiler tool window opened on the Profiling tab with the profiling controller inside.

3. Reproduce the issue you are looking for or, if you just want to evaluate the memory usage, go through the desired usage scenarios in your application. Note that currently, it's not possible to get memory snapshots. You can analyze only memory allocation.

4. After you collect the data, you can finish the profiling session. Normally, you do it either by closing the profiled application or by detaching the profiler via the Detach button ( Kill forcibly terminates the profiled app and the session, so, use it only in emergency cases).

5. Analyze the collected data.

Create a custom profiling configuration

1. In the menu, choose Run | Switch Profiling Configuration | Edit Configurations.

2. In the opened Profiling Configurations window, click to add a new profiling configuration.

3. In the list, select a data collection mode: either Memory (Sampled allocations), or Memory (Full allocations). Learn more about the modes.

4. Specify configuration Name and other profiling options:

   Control profiling manually

   Enables you to control profiling manually via the profiler controls.

   Control profiling via API

   Enables you to control profiling directly from the code of the profiled application. Learn more about using the API in the dotMemory documentation.

   Profile child processes

   If selected, dotMemory will profile not only the main app process but the processes it runs as well.