Once the profiled application is running, you should connect to it to obtain and analyze profiling results.
Connect to locally running profiled application
The profiler will show all detected locally running profiled applications on the Welcome screen:
A "locally running profiled application" is an application running and being profiled on the same computer where you are now using the profiler UI.
Connect to remote application
To connect to a profiled application that is running on a remote computer,
use File | Connect to Remote Application....
You can simply specify the host (name or IP address) of the remote computer where the profiled application(s) is (are) running. In this case the profiler tries to automatically detect the profiled applications on ports in some predefined range. When the profiled application starts, the profiler agent first tries to use a port in this range, thus enabling an automatic scan of the applications on remote host.
In connected mode
After a connection is established successfully, the profiling session tab opens. It contains the toolbar to control profiling and displays application telemetry.
1. Capture Performance Snapshot - save the profiling results to a file, which can be opened later
2. CPU Profiling controls
3. Capture Memory Snapshot
4. Force Garbage Collection
5. 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.