Collecting Concurrency Data for a Service 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.

Note

Enhanced security features in Windows 8 and Windows Server 2012 required significant changes in the way the Visual Studio profiler collects data on these platforms. Windows Store apps also require new collection techniques. See Profiling Windows 8 and Windows Server 2012 applications.

Common Tasks

Task	Related Content
Attach to a running .NET service	How to: Attach the Profiler to a .NET Service to Collect Concurrency Data by Using the Command Line
Add tier-interaction data	How to: Add Tier Interaction Data to Profiling Data From the Command Line
Attach to a running C/C++ service	How to: Attach the Profiler to a Native Service to Collect Concurrency Data by Using the Command Line

Related Tasks

Profiling Windows Services

Task	Related Content
Profile by using the sampling method	Collecting Application Statistics for Services by Using the Profiler Sampling Method
Profile by using the instrumentation method	Collecting Detailed Timing Data for Services by Using the Instrumentation Method from the Profiler Command Line
Profile.NET memory allocation and garbage collection	Collecting Memory Data from .NET Framework Services by Using the Profiler Command Line

Profiling Concurrency Data

Task	Related Content
Profile stand-alone applications	Collecting Concurrency Data for Stand-Alone Applications by Using the Profiler Command Line
Profile ASP.NET Web applications	Collecting Concurrency Data for an ASP.NET Web Application Using the Profiler Command Line

Analyzing Concurrency Data Views and Reports

Resource Contention Data Views

Concurrency Visualizer

Reference

Command-Line Profiling Tools Reference