Measure application performance from the command line

You can collect performance information about an application by using command-line tools. You can collect performance data for CPU Usage, .NET memory allocation, instrumentation, and database queries.

In the example described in this article, you collect performance information for Microsoft Notepad, but the same method can be used to profile any process.

Note

For C/C++ instrumentation from the command line, see Instrument a native stand-alone component. For CPU usage data, you can use the procedures described in this article.

Prerequisites

• Visual Studio 2019 or later versions

• Familiarity with command-line tools

• To collect performance information on a remote machine without Visual Studio installed, install the Remote Tools for Visual Studio on the remote machine. The version of the tools must match your version of Visual Studio.

Collect performance data

Profiling using the Visual Studio Diagnostics CLI tools works by attaching the profiling tool, along with one of the collector agents, to a process. When you attach the profiling tool, you begin a diagnostic session that captures and stores profiling data until the tool is stopped, at which point that data is exported into a .diagsession file. Then you can open this file in Visual Studio to analyze results.

1. Start Notepad, and then open Task Manager to get its process ID (PID). In Task Manager, find the PID in the Details tab.

2. Open a command prompt and change to the directory with the collection agent executable, typically here (for Visual Studio Enterprise).

   <Visual Studio installation folder>\2022\Enterprise\Team Tools\DiagnosticsHub\Collector\

   For the remote tools, the collection agent executable is in this location:

   Program Files\Microsoft Visual Studio 17.0\Team Tools\DiagnosticsHub\Collector\

   Note

   When using the command line in remote scenarios, you need to run the command-line instructions on the remote machine. If you want to attach to the remote machine from Visual Studio, use the Performance Profiler in Visual Studio instead.

3. Start VSDiagnostics.exe by typing the following command.

   VSDiagnostics.exe start <id> /attach:<pid> /loadConfig:<configFile>
   

   The arguments that must be included are:

   • <id> Identifies the collection session. The ID must be a number between 1-255.
   • <pid>, PID of the process you wish to profile, in this case the PID you found in step 1.
   • <configFile>, configuration file for the collection agent you wish to launch. For more information, see Configuration files for agents.

   For example, you could use the following command for the CPUUsageBase agent by replacing the pid as described previously.

   VSDiagnostics.exe start 1 /attach:<pid> /loadConfig:AgentConfigs\CPUUsageLow.json
   

   Alternatively, you can use the launch command to start an executable. In this scenario, you don't need to get the process ID and attach to it. All tools support the launch command, although some do not support attach, such as the Instrumentation and .NET Allocation tool. For example, use the following to start an executable and collect instrumentation data:

   VSDiagnostics start <id> /launch:<ExeToProfile> /loadConfig:AgentConfigs\PerfInstrumentation.json
   

4. Resize Notepad, or type something in it in order to make sure that some interesting profiling information is collected.

5. Stop the collection session and send output to a file by typing the following command.

   VSDiagnostics.exe stop <id> /output:<path to file>
   

6. Locate the .diagsession file output from the previous command, and open it in Visual Studio (File > Open) to examine the information collected.

   To analyze the results, see the documentation for the corresponding performance tool. For example, this might be the CPU Usage, .NET Object Allocation tool, Instrumentation, or the Database tool.

Agent configuration files

Collection Agents are interchangeable components that collect different types of data depending on what you are trying to measure.

For convenience, we recommend that you store that information in an agent configuration file. The configuration file is a .json file that contains at minimum the name of the .dll and its COM CLSID. By default, you can find the example configuration files in the following folder:

Program Files\Microsoft Visual Studio\<version>\<sku>\Team Tools\DiagnosticsHub\Collector\AgentConfigs

CpuUsage configurations (Base/High/Low) correspond to data collected for the CPU Usage profiling tool. DotNetObjectAlloc configurations (Base/Low) correspond to data collected for the .NET Object Allocation tool.

Base/Low/High configurations refer to the sampling rate. For example, Low is 100 samples/second and High is 4000 samples/second.

For the VSDiagnostics.exe tool to work with a collection agent, it requires both a DLL and a COM CLSID for the appropriate agent. The agent might have additional configuration options as well, which would be any options that are specified in the config file, formatted as properly escaped JSON.

Permissions

To profile an application that requires elevated permissions, you must do so from an elevated command prompt.