We recommend using Visual Studio 2017

Collecting Concurrency Data for Stand-Alone Applications by Using the Profiler Command Line

 

The new home for Visual Studio documentation is Visual Studio 2017 Documentation on docs.microsoft.com.

The latest version of this topic can be found at Collecting Concurrency Data for Stand-Alone Applications by Using the Profiler Command Line.

The concurrency method of Visual Studio Profiling Tools enables you to collect resource contention data and thread activity data that shows you CPU utilization, thread contention, thread migration, synchronization delays, areas of overlapped IO, and other system events.

TaskRelated content
Start a .NET Framework application and profile concurrency data- How to: Launch a .NET Framework Application to Collect Concurrency Data
Start a C/C++ application and profile concurrency data- How to: Launch a Native Application to Collect Concurrency Data
Attach the profiler to a running .NET Framework application- How to: Attach the Profiler to a .NET Framework Application to Collect Concurrency Data
Attach the profiler to a running C/C++ application- How to: Attach the Profiler to a Native Application and Collect Concurrency Data

Profiling Stand-Alone Applications

TaskRelated content
Profile by using the sampling method- Collecting Application Statistics Using Sampling
Profile by using the instrumentation method- Collecting Detailed Timing Data Using Instrumentation
Profile .NET memory allocation and garbage collection- Collecting .NET Framework Memory Data
Adding tier-interaction data- Collecting tier interaction data

Profiling Concurrency Issues

TaskRelated content
Profile ASP.NET applications- Collecting Concurrency Data
Profile services- Collecting Concurrency Data

Analyzing Concurrency Data Views and Reports

Resource Contention Data Views

Concurrency Visualizer

Command-Line Profiling Tools Reference

Show: