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

System_CAPS_ICON_note.jpg 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 Performance Tools on Windows 8 and Windows Server 2012 applications.

TaskRelated Content
Attach to a running .NET service- How to: Attach the Profiler to a .NET Service to Collect Concurrency Data
Add tier-interaction data- Collecting tier interaction data
Attach to a running C/C++ service- How to: Attach the Profiler to a Native Service to Collect Concurrency Data

Profiling Windows Services

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 Memory Data

Profiling Concurrency Data

TaskRelated Content
Profile stand-alone applications- Collecting Concurrency Data
Profile ASP.NET Web applications- Collecting Concurrency Data

Analyzing Concurrency Data Views and Reports

Resource Contention Data Views

Concurrency Visualizer

Command-Line Profiling Tools Reference

Show: