How to analyze ASP. NET web application performance by using the performance administration tool

This step-by-step article describes how to analyze ASP. NET
Web application performance by using the performance administration tool.

ASP. NET provides a lot of information through standard performance
Counters. The standard performance counters can be monitored by using
Performance snap-in. This information is useful for system administrators who
Must understand the performance characteristics of an ASP. NET application.
Performance counters can reveal the time it takes to render pages, the burden
Placed on the processor, and the number of active ASP. NET sessions.

Monitoring these key Counters is useful under the circumstances that
Follow:

• You can create a performance baseline and then use this
  Baseline to measure the impact of configuration changes and Application
  Upgrades.
• You can validate changes that are made to the configuration
  Of an application specifically to improve performance.
• You can verify that hardware upgrades have the effect that
  You want on performance.
• You can monitor the performance of the application under
  Load. The load can be either real or artificially generated by a tool such
  The Web application stress tool.
• You can determine the performance impact of Application
  Upgrades.

This article describes the most important counters that you can
Use to analyze the performance of ASP. NET applications. This is not a complete
List of ASP. NET counters. Only the minimal counters that you must have to gauge
The performance of an application are described.

Key Performance Monitor counters

These counters are most easily viewed by using the performance
Snap-in. To run the performance snap-in, follow this steps:

1. On the taskbar, clickStart
   , Point
   Settings
   , And then clickControl
   Panel
   .
2. Double-clickAdministrative Tools
   Folder and then double-clickPerformance
   Tool.
3. When the performance snap-in starts, click to select
   System Monitor
   Object in the left pane and then click
   Add
   On the tool bar to add the counters that are described in
   The following table.

   Performance object	Counter	Instance (if Necessary)	Description
   Process	% Processor time	Aspnet_wp	The percentage of the time that is processor time Consumed by ASP. NET. When you compare performance under standard load against Previusly captured baseline, decreases in this counter reveal lower Processor Requirements, and therefore greater scalability.
   Process	Working Set	Aspnet_wp	The Quantity of memory that is actively used by ASP. NET. While the application Developer has the most control over how memory is consumed by the application, System Administrators can have a significant impact by adjusting the session Time-out period.
   ASP. NET Applications	Requests/sec	_ Total __	When you analyze Performance against an artificially generated load, this counter permits you Verify that requests are handled as quickly as they are sent. If the number Requests per second falls below the number of requests that are generated per Second, queuing is occurring. This means that the maximum request rate has been Surpassed. When you analyze actual user load in a production environment, this Counter reveals how busy the site is.
   ASP. NET Applications	Sessions Active	_ Total __	This counter shows the number of ASP. NET Sessions that have been created but have not timed out. Session-enabled ASP. NET Applications create a new session when a user request is submitted without Cookie. sessions are removed when the application destroys the session or when The session times out. By default, ASP. NET sessions time out after 20 minutes. Each session consumes memory. Therefore, if you reduce the session time-out, You may improve performance if the session uses a large quantity of memory, and A significant number of sessions are active. Monitor the working set counter Measure the impact that session time-out has on memory consumption.
   ASP. NET	State Server sessions Active		This counter shows the same information as the sessions Active counter inASP. NET application performance Object. Use this counter when a State server is used instead In-process sessions.
   ASP. NET	Request execution Time		This counter shows the time, in milliseconds, that it Takes to render the last requested page and then transmit it to the user. This Counter will generally be greater than the time a trace shows to render Page. This counter is a more comprehensive measurement of start-to-finish Request time. If this counter shows a lower average when compared to Baseline, then both the scalability and the performance of the application have Been increased.