Collect statistics for ASP.NET web apps
This section describes the procedures and options for collecting performance statistics for an ASP.NET Web application by using the VSPerfASPNETCmd and VSPerfCmd command-line tool and the sampling profiling method.
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.
Although the VSPerfCmd tool gives you complete access to Profiling Tools functionality, including pausing and resuming profiling, and collecting additional data from processor and Windows performance counters, you should use the VSPerfASPNETCmd command line tool when you do not need this functionality. The VSPerfASPNETCmd command line tool is the preferred method when your are profiling ASP.NET Web sites using the stand-alone profiler. Compared with the VSPerfCmd command line tool, no environment variables need to be set, and rebooting the computer is not required. For more information, see Rapid web site profiling with VSPerfASPNETCmd.
|Attach the profiler to an ASP.NET application||- How to: Attach the profiler to an ASP.NET web application to collect application statistics|
Profile ASP.NET web applications
|Profile by using the instrumentation method||- Collect detailed timing data using instrumentation|
|Profile memory allocation and garbage collection||- Collect memory data|
|Profile resource contention and thread activity||- Collect concurrency data|
|Profile stand-alone (client) applications||- Collect application statistics using sampling|
|- Profile services||- Collect application statistics using sampling|
Analyze sampling data views and reports