Collecting Memory Data from an ASP.NET Web Application 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
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 |
Related Tasks
Profiling ASP.NET Web Applications
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 resource contention and thread activity | - Collecting Concurrency Data |
Profiling .NET Framework Memory Data
Task | Related Content |
---|---|
Profile stand-alone (client) applications | - Collecting .NET Framework Memory Data |
Profile services | - Collecting .NET Memory Data |