Collect memory data from an ASP.NET web application 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

This section describes the procedures and options for collecting memory allocation and object lifetime data for an ASP.NET web application by using the VSPerfCmd command-line tool.

Note

The VSPerfCmd tool provides you with complete access to Profiling Tools functionality, including pausing and resuming profiling, and collecting additional data from processor and Windows performance counters. You can also use the VSPerfASPNETCmd command-line tool when you do not need this functionality. 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.

Common tasks

Task Related Content
Attach the profiler to a running ASP.NET application - How to: Attach the profiler to an ASP.NET web application to collect memory data
Instrument statically compiled binaries - How to: Instrument a statically compiled ASP.NET application and collect memory data
Instrument dynamically compiled binaries - How to: Instrument a dynamically compiled ASP.NET application and collect memory data

Profile ASP.NET web applications

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 resource contention and thread activity - Collect concurrency data

Profile .NET Framework memory data

Task Related Content
Profile stand-alone (client) applications - Collect .NET Framework memory data
Profile services - Collect .NET memory data

Analyze .NET memory data views and reports

Reference