How to: Instrument a Statically Compiled ASP.NET Web Application and Collect Memory Data by Using the Profiler Command Line
This topic describes how to use Visual Studio Team System Developer Edition Profiling Tools command-line tools to instrument a pre-compiled ASP.NET Web component or Web site and collect .NET memory allocation, object lifetime, and detailed timing data.
To collect data from a ASP.NET Web component by using the instrumentation method, you use the VSInstr.exe tool to generate an instrumented version of the component. On the computer that hosts the component, you replace the non-instrumented version of the component with the instrumented version. You then use the VSPerfCLREnv.cmd tool to initialize the global profiling environment variables and restart the host computer. You then start the profiler.
When the instrumented component is executed, timing data is automatically collected to a data file. You can pause and resume data collection during the profiling session.
To end a profiling session, you close the ASP.NET worker process that hosts the component and then explicitly shut down the profiler. In most cases, we recommend clearing the profiling environment variables at the end of a session.
To instrument an ASP.NET Web component and start profiling
Use the VSInstr tool to generate an instrumented version of the target application. If necessary, replace the application binaries on the ASP.NET host computer with the instrumented binaries.
Open a command prompt window. If necessary, add the profiler tools directory to your PATH environment variable. The path is not added at installation.
32 bit computers
On 32 bit computers, the default profiler tools directory is
\Program Files\Microsoft Visual Studio 9.0\Team Tools\Performance Tools.
64 bit computers
On 64 bit computers, specify the path according to the target platform of the application to be profiled.
To profile 32 bit applications, the default profiler tools directory is
\Program Files (x86)\Microsoft Visual Studio 9.0\Team Tools\Performance Tools
To profile 64 bit applications, the default profiler tools directory is
\Program Files (x86)\Microsoft Visual Studio 9.0\Team Tools\Performance Tools\x64
For example, to add the profiler directory to PATH on a 32 bit computer, type
set path=%path%;C:\Program Files\Microsoft Visual Studio 9.0\Team Tools\Performance Tools
Initialize the .NET profiling environment variables. In a command prompt window, type:
/globaltracegc collects .NET memory allocation and timing data.
/globaltracegclife collects .NET memory allocation, object lifetime, and detailed timing data.
Restart the computer.
Open a command prompt window. If necessary, set the profiler path environment variable.
Start the profiler. In a command prompt window, type:
VSPerfCmd /start:trace /output:OutputFile [Options]
The /start:trace option initializes the profiler.
The /output:OutputFile option is required with /start. OutputFile specifies the name and location of the profiling data (.vsp) file.
You can use any of the following options with the /start:trace option.
The /user and /crosssession options are usually required for ASP.NET applications.
Open the Web site that contains the instrumented component.
While the target application is running, you can control data collection by starting and stopping the writing of data to the file by using VSPerfCmd.exe options. Controlling data collection enables you to collect data for a specific part of program execution, such as starting or shutting down the application.
To start and stop data collection
The following pairs of options start and stop data collection. Specify each option on a separate command line. You can turn data collection on and off multiple times.
You can also use the VSPerfCmd.exe /mark option to insert a profiling mark into the data file. The /mark command adds an identifier, a timestamp, and an optional user-defined text string. Marks can be used to filter the data in profiler reports and data views.
To end a profiling session, close the ASP.NET Web application, and then use the Internet Information Services (IIS) IISReset command to close the ASP.NET worker process. Call the VSPerfCmd /shutdown option to turn the profiler off and close the profiling data file. The VSPerfClrEnv /globaloff command clears the profiling environment variables. You must restart the computer for the new environment settings to be applied.
To end a profiling session
Close the ASP.NET Web application.
Close the ASP.NET worker process. Type:
Shut down the profiler. Type:
(Optional). Clear the profiling environment variables. Type:
Restart the computer. If necessary, restart IIS. Type: