Collecting Concurrency Data for a Service by Using the Profiler Command Line
Note
This article applies to Visual Studio 2015. If you're looking for the latest Visual Studio documentation, see Visual Studio documentation. We recommend upgrading to the latest version of Visual Studio. Download it here
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 Performance Tools on 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 |
| 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 |
Related Tasks
Profiling Windows Services
| Task | Related 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
| Task | Related 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