For example, this might be the CPU Usage. To analyze the results, see the documentation for the corresponding performance tool. diagsession file output from the previous command, and open it in Visual Studio ( File > Open) to examine the information collected. Stop the collection session and send output to a file by typing the following command. Resize Notepad, or type something in it in order to make sure that some interesting profiling information is collected. VSDiagnostics.exe start 1 /attach: /loadConfig:AgentConfigs\CPUUsageLow.json For more information, see Configuration files for agents.įor example, you could use the following command for the CPUUsageBase agent by replacing the pid as described previously.
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. Profiling using the Visual Studio Diagnostics CLI tools works by attaching the profiling tool, along with one of the collector agents, to a process. The version of the tools must match your version of Visual Studio. To collect performance information on a remote machine without Visual Studio installed, install the Remote Tools for Visual Studio on the remote machine. 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. You can collect performance information about an application by using command-line tools. Applies to: Visual Studio Visual Studio for Mac Visual Studio Code
0 kommentar(er)
