Top 10 Favorite Performance Counters in Web Site Load Testing Using VSTS 2008

Microsoft Visual Studio Team System/Test Edition provides an excellent tool to perform web site load testing. Using this load testing tool, you can monitor and measure the site performance along with system status with respect to a given load/stress.

Fortunately VSTS provides a support for wide range of performance counters, from web page request per second to condition of physical disk, memories. Unfortunately, they are too huge that, initially testers/designers get overwhelmed with all of those, to find out a clear idea about the performance of the site they built.

The number of counter parameters to be considered by the load tester/designers is greatly varies based on the type and size of the web application to be tested. Here is my favorite top 10 performance counters that I use on my each load tests, regardless of project size. These counters are based two primary categories: Web Site end and Hardware end.

SoftwareTesting

Web Site Related Performance Counters

Web site related performance counters are the counters that provide valuable information about the health of web site that is under test. These parameters are categorized as Requests, Pages, Tests and Errors.

1. Request - Avg Req/Sec

Desired value range: High

This is the average number of requests per second, which includes failed and passed requests, but not cached requests, because they are not issued on web server. Please note that, all http requests, such as image, java-script, aspx, html files generates separate/individual/single request .

2. Request -    Avg Req Passed/Sec

Desired value range: High

While “Request - Avg Req/Sec” provides an average with respect to all passed and failed request, “Request -    Avg Req Passed/Sec” provided the average of passed requests. This info also helps to determine the average number of failed requests/sec.

3. Page -        Avg Page Time (Sec)

Desired value range: Low

While a single request refers to request to a single http elements (such as css, java-script files, images, aspx, html etc), a page is the container of all of the corresponding requests generated when a web page is requested (for instance via the browser address bar). “Page -        Avg Page Time (Sec)” counter refers to the average of total time taken to load a page with all of its http elements.

4. Test -        Total Test

Desired value range: High

For instance, we have created a web test, that contains two web pages, pushing on a button on the first page will re-direct the user to the second page, although there will be multiple entries will be involved for Requests and Pages counters, but the whole process will be considered as a single Test.

This counter considers the total number of tests (which includes passed and failed tests) during the test period.

5. Scenario -        User Load

Desired value range: High

This counter considers the maximum user load that has been provided during the test run. Please note that, for Step Load pattern, where more user volume is added on step by step basis, the maximum user load will be counted through this counter parameter.

6. Errors -    Errors/Sec

Desired value range: Low

Includes average number of errors occurred per second, which includes all types of errors.

snap2

Hardware Related Performance Counters

7. Processor -    % Processor Time

Desired value range: Low

This is the number of processor time being utilized in percentage.

8. Memory -    Available MBytes

Desired value range: High

This the amount of Memory available in Mega byte.

9. Physical Disk -        Current Disk Queue Length

Desired value range: Low

It shows how many read or write requests are waiting to execute to the disk. For a single disk, it should idle at 2-3 or lower.

10. Network Interface -    Output Queue Length

Desired value range: Low

This is the number of packets in queue waiting to be sent. A bottleneck needs to be resolved if there is a sustained average of more than two packets in a queue.

Download the SQL Script which selects all of the parameters as mentioned above with respect to the latest load test, from here:

 

 


kick it on DotNetKicks.com

Print | posted on Thursday, February 19, 2009 3:12 PM

Feedback

# re: Top 10 Favorite Performance Counters in Web Site Load Testing Using VSTS 2008

left by Max at 3/4/2009 12:53 AM Gravatar
Hi,

Really nice explanation and details.

Thanks a lot!

Max

# re: Top 10 Favorite Performance Counters in Web Site Load Testing Using VSTS 2008

left by Nitin at 7/19/2009 10:27 PM Gravatar
Hi,

Fantastic explanation!

One thing i want to know, Where should we check counters... where should we check on client machine or server where the application is deployed?

# re: Top 10 Favorite Performance Counters in Web Site Load Testing Using VSTS 2008

left by Saumitra at 12/10/2009 6:03 PM Gravatar
Very useful information !

I wanted some more information on Avg. Req/sec. We had performed a load test for a web application, which was a simple web form, with 1 constant user. But the Req/sec. generated were almost close to 800 !! Is there any way this can be controlled ?

# re: Top 10 Favorite Performance Counters in Web Site Load Testing Using VSTS 2008

left by Ana at 2/10/2010 3:33 PM Gravatar
This article is very well explained. However, I want to get more details about VSTS. How does it work when you do a web site load testing?

# re: Top 10 Favorite Performance Counters in Web Site Load Testing Using VSTS 2008

left by PK Tester at 4/22/2010 3:29 AM Gravatar
Ye, very nice explanation.

I was wondering why the requests/sec counter was so high compared to my user load.

Thanks again.

# re: Top 10 Favorite Performance Counters in Web Site Load Testing Using VSTS 2008

left by Jitendra at 5/15/2010 9:04 PM Gravatar
This article is very well explained and provided basics guideline for counters uses

# re: Top 10 Favorite Performance Counters in Web Site Load Testing Using VSTS 2008

left by Nauman at 6/3/2010 7:34 PM Gravatar
# re: Top 10 Favorite Performance Counters in Web Site Load Testing Using VSTS 2008
Hi,

Fantastic explanation!

One thing i want to know, Where should we check counters... where should we check on client machine or server where the application is deployed? 7/19/2009 10:27 PM | Nitin


I also want to know about this

# re: Top 10 Favorite Performance Counters in Web Site Load Testing Using VSTS 2008

left by Sherin Samuel at 6/16/2010 6:33 PM Gravatar
Detailed explanation, in a simple way, its good.
Post A Comment
Title:
Name:
Email:
Comment:
Verification: