Share via


Collect concurrency data for a service by using the profiler command line

Applies to: yesVisual Studio noVisual Studio for Mac

Note

This article applies to Visual Studio 2017. 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. UWP 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 - Collect tier interaction data
Attach to a running C/C++ service - How to: Attach the profiler to a native service to collect concurrency data

Profile Windows services

Task Related Content
Profile by using the sampling method - Collect application statistics using sampling
Profile by using the instrumentation method - Collect detailed timing data using instrumentation
Profile.NET memory allocation and garbage collection - Collect .NET memory data

Profile concurrency data

Task Related Content
Profile stand-alone applications - Collect concurrency data
Profile ASP.NET Web applications - Collect concurrency data

Analyze concurrency data views and reports

Reference