Command-Line Profiling of Services

This section describes the procedures and options for collecting performance data for Windows services by using Visual Studio Profiling Tools from the command line.

Common Tasks

Task	Related Content
Collect application statistics: Use the sampling method to collect performance statistics. Sampling data is useful for analyzing CPU utilization issues and for understanding the general performance characteristics of an application.	Collecting Application Statistics for Services by Using the Profiler Sampling Method
Collect detailed timing data: Use the instrumentation method to collect detailed timing information. Instrumentation data is useful for analyzing IO issues and for fine-grained analysis of application scenarios.	Collecting Detailed Timing Data for Services by Using the Instrumentation Method from the Profiler Command Line
Collect .NET memory data: Use sampling or instrumentation to collect .NET memory allocation data that shows you the size and number of allocated objects. You can also collect object lifetime data that shows you the size and number of objects that are reclaimed in each garbage collection generation.	Collecting Memory Data from .NET Framework Services by Using the Profiler Command Line
Collect concurrency data: Use the concurrency method 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.	Collecting Concurrency Data for a Service by Using the Profiler Command Line
Add tier interaction data: You can add performance data about synchronous ADO.NET calls that the service made to a Microsoft SQL Server database.	How to: Add Tier Interaction Data to Profiling Data From the Command Line

Related Tasks

Task	Related Content
Profile stand-alone (client) applications	Command-Line Profiling of Stand-Alone Applications
Profile ASP.NET applications	Command-Line Profiling of ASP.NET Web Applications