How I may help
LinkedIn Profile Email me!
Call me using Skype client on your machine


Reload this page LoadRunner Analysis Statistics and Graphs

This page explains the sample Summary Report generated by LoadRunneranother page on this site and then, more importantly, explain how to make use of them to make decisions.

Pop-up a sample report in a new window (this may take a few seconds)

 

Topics:
on this page Analysis Summary
on this page Statistics Summary
on this page Transaction Summary
on this page HTTP Responses Summary
on this page Standard Graphs
on this page TPS Explained
on this page Changing Graphs & Templates
on this page Your comments?

 

RSS XML feed for load testers RSS preview for load testers Site Map List all pages on this site 
About this site About this site 
Go to first topic Go to Bottom of this page


Set screen Analysis Summary

"Autumn Landscape 05" by Ioan Popei

Set screen Statistics Summary

Set screen Transaction Summary

Set screen HTTP Responses Summary

Set screen Standard Graphs (Provided by Default)

    
    	Vusers
    	Transactions
    	Web Resources
    	System Resources
    	Web Server Resources
    	Web Page Breakdown
    	
    These graphs are sequenced according to the sequence in Controller menu option Graph > Add Graph... During Analysis this order is automatically applied from our custom Template.

    Remember that line graphs trail off during processing ramp-down time.

Graph Category Graph Note

Vusers

Click to enlarge sample in new window
Running Vusers
This line graph shows the impact of Ramp-Up and Ramp-Down specified for run-time. This also shows the time when Errors begin to occur during the test run.

Note the time when the Number of Vusers peaks and when it begins to drop off. This is the "steady state" period of the run.

Transactions

Click to enlarge sample in new window
Average Transaction Response Time
This line graph is used to determine whether performance is within acceptable minimum and maximum transaction performance time ranges expected of the system. It displays the average time taken to perform transactions during each second of the load test. Unlike the Summary Report, only Transaction End Status of Passed are included (Failed transactions are filtered out by default).
Click to enlarge sample in new window
Transactions per Second
This line graph helps you determine the actual load imposed by each transaction action at various spans of time throughout a run.

Each line displays the number of transactions performed — both passed(successful) and failed(unsuccessful) transactions.

Each point on a line is calculated from the number of transactions that ended within each span of time (the Granularity period automatically set to the lowest allowed relative to the scenario run). For example, an Average data point of 0.5 within the Granularity period of 16 Seconds means that 8 (0.5 x 16) transactions were completed within that 16 second period.

Set screen TPS (Transactions Per Second) Explained

TPS is the count of transactions processed each second. Like Miles Per Hour, it is a measurement of speed.

One second
A A A A
.25 .25 .25 .25
One second
B B
.5 .5

In this illustration, when each action is performed on its own,
action A has a TPS of 4 per second.
Action B has a TPS of 2 per second.

Note that:

  1. Think time decreases TPS

  2. Errors increases TPS because failed transactions end sooner than good transactions which complete processing.

  3. Multiple actions performed in a linked sequence decreases TPS:

    One second
    A B A
    .25 .5 .25

    When actions are performed in sequence,
    action A now individually has a TPS of 2 per second and
    action B individually has a TPS of 1 per second.

    However, the combination of multiple actions average together to 3 per second.

Click to enlarge sample in new window
Total Transactions per Second
This graph helps you determine the actual total transaction load on your system at any given moment in time. This line chart displays the total of all transaction actions performed during each second of a load test.

An additional line is used to display the total number of Failed (unsuccessful) transactions.

Click to enlarge sample in new window
Transaction Summary
This bar graph displays, by transaction action, how many transactions passed, failed, stopped, or ended with errors.
Click to enlarge sample in new window
Transaction Performance Summary
This bar chart displays the minimum, average, and maximum response time for each transaction action in the load test.

This chart was manually scaled down to make actions easier to interpret. The tall column action on the left summarizes all other transaction actions by a user.

Click to enlarge sample in new window
Transaction Response Time Under Load
This XY graph illustrates how the Number of Vusers impacts Response Time. Typically, individual response times follow an exponential curve up as servers strain to process more Vusers. A flat horizontal line means that response time does not vary, usually because the system has enough (or too much) capacity.

Web Resources

Click to enlarge sample in new window
Hits per Second
The one line on this graph helps you evaluate the amount of load Vusers generate, in terms of the number of hits to all web servers. It displays the number of hits made on all Web servers by Vusers during each second of the load test.
Click to enlarge sample in new window
Hits Summary
This pie chart displays the number of hits made on the Web server by Vusers. This graph helps you evaluate, in terms of the number of hits, the amount of load Vusers generate.

Click to enlarge sample in new window
Throughput
This line chart helps you to evaluate the amount of load Vusers generate on network resources. It displays the raw amount of bytes that the Vuser client received each second as a result of the hits on the web server during load testing.

Click to enlarge sample in new window
Throughput Summary
This pie chart illustrates values in the Total Throughput (bytes) presented in the Summary report.

Click to enlarge sample in new window
HTTP Responses per Second

Click to enlarge sample in new window
Connections

Click to enlarge sample in new window
Connections per Second
This line graph displays the number of HTTP & HTTPS Connections requested of all web servers. The graph displays different lines for New Connections and Connection Shutdowns.

Click to enlarge sample in new window
SSLs Per Second
This line graph only appears when web apps use HTTPS from servers with SSL certificates installed, commonly associated with login transactions which require added security.

This line graph displays the number of New and Reuse Sessions processed per second.

System Resources

UNIX Resources:
Captured by LoadRunner issuing uptime command.
Click to enlarge sample in new window
UNIX CPU Util
Each line on this graph displays for each Linux GH9 server the percent of CPUs are busy. It is obtained using the vmstat or sar command. The maximum is 400 for a 4 CPU machine.
UNIX Avg Load- Last 60 sec (one minute)
Background monitoring (rstatd and rup) consumes about 0.02 on loadtest7.
UNIX Paging rate
Each line on this graph displays for each Linux GH9 server the rate pages are swapped in and out of memory.

Average of 15-25 is expected from Linux RH9 servers at rest. When loadtest9 is re-populating mysql, this can jump to a max of 25,000.

Web Server Resources

Apache:
Captured by LoadRunner issuing http://loadtest4/ server-status

Large differences between servers may be due to the Load Balancer.

#Busy Servers and #Idle Servers
Click to enlarge sample in new window
Apache CPU Usage
Each line on this graph displays the number of CPU Resource used on an individual web server.

Differences in usage among web servers may indicate issues with the load balancing method or configuration differences among web servers.

Click to enlarge sample in new window
Apache Hits/sec
Each line on this graph displays the number of hits coming through an individual web server each second.
Click to enlarge sample in new window
Apache KBytes Sent/sec
Each line on this graph displays the number of raw Kilobytes coming through an individual web server, similar to the UNIX netstat command. At rest, each server averages 0.150 of keep-alive traffic.

Web Page Breakdown

Click to enlarge sample in new window
Web Page Breakdown
This graph lists the average download time for each transaction action.
Click to enlarge sample in new window
Page Component Breakdown
This pie chart shows how much each component is a percentage of the sum of Average download time (in seconds).
Download Component Size (KB)

Caution on scaling: Please focus on the numbers and avoid comparing lines on the same graph because the automatic scaling of individual metrics currently does not scale like metrics simularly.

The scale of each graph is manually set.

Go to Top of this page. Set screen Changing Charts and Templates

Go to Top of this page. Set screen Multiple Dimmensional Variables

Go to Top of this page. Set screen Cross Compare Results

Portions ©Copyright 1996-2011 Wilson Mar. All rights reserved. | Privacy Policy |


How I may help

Send a message with your email client program


Your rating of this page:
Low High




Your first name:

Your family name:

Your location (city, country):

Your Email address: 



  Top of Page Go to top of page

Thank you!