LoadRunner Report

Date: 7/28/2011

1. Executive Summary ....................................................................3 1.1. Objectives ..........................................................................3 1.2. Analysis Session Summary ........................................................3 1.3. Conclusions .........................................................................4 2. Scenario Configuration.................................................................5 2.1. Files .................................................................................5 2.2. Scheduler Information ............................................................5 2.3. Scripts ...............................................................................5 2.4. Run Time Settings .................................................................5 2.4.1. Multi+QTWeb ............................................................................................ 5 3. Users' Influence .........................................................................6 4. Hits Per Second .........................................................................7 5. Vuser Load Scheme .....................................................................8 6. Transaction Response Times ..........................................................9 7. Terminology ........................................................................... 10 7.1. LoadRunner Objects............................................................. 10 7.2. Graph Information ............................................................... 10

1. Executive Summary
1.1. Objectives
Add text here

1.2. Analysis Session Summary

Analysis Summary
Scenario Name: Duration: Scenario1 11 minutes and 24 seconds.

Period: 28/07/2011 23:03:08 - 28/07/2011 23:14:32

Results in Session: C:\Documents and Settings\loadrunner\Local Settings\Temp\res\res.lrr

Statistics Summary

Maximum Running Vusers: Total Throughput (bytes): Average Throughput (bytes/second): Total Hits: Average Hits per Second:

2 2,843,247 4,151 2,100 3.066 View HTTP Responses Summary

Scenario Behavior Over Time

The SLA status of the following measurements displayed over time. You can select a specific time range for each transaction in order to analyze the time range.

Measurement Name Application Under Test Errors

Time Ranges 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0

4
00:00:00 00:00:35 00:01:15 00:01:55 00:02:30 00:03:10 00:03:50 00:04:25 00:05:05 00:05:45 00:06:20 00:07:00 00:07:40 00:08:15 00:08:55 00:09:35 00:10:10 00:10:50

Transaction Summary

Transactions:

Total Passed: 74

Total Failed: Total Stopped: 0 0

Average Response Time

Transaction Name Action_Transaction vuser_end_Transaction vuser_init_Transaction

SLA Status

Minimum Average Maximum 11.613 0 0.002 12.37 0 0.002 13.095 0 0.002

Std. Deviation 0.352 0 0

90 Percent 12.896 0 0.002

Pass Fail Stop 70 2 2 0 0 0 0 0 0

Service Level Agreement Legend:

Pass

Fail

No Data

HTTP Responses Summary

HTTP Responses HTTP_200

Total 2,100

Per second 3.066

1.3. Conclusions
Add text here

2. Scenario Configuration
2.1. Files
Name: Results in Session: Session Name: Scenario1 C:\Documents and Settings\loadrunner\Local Setting s\Temp\res\res.lrr Session1.lra

2.2. Scheduler Information

Started On: Ended On: Duration: Load Behavior: 28/07/2011 28/07/2011 23:03:08 23:14:33

Load all Vusers simultaneously

2.3. Scripts
Script test3 Type Multi+QTWeb File C:\Program Files\Mercury Interactive\Mercury LoadRunner\scripts\test3\test3.usr

2.4. Run Time Settings

2.4.1. Multi+QTWeb
Group test3 Script test3 Pacing As soon as possible Think Time Replay as recorded Network Speed Maximum bandwidth Browser cache Yes

3. Users' Influence
Displays average transaction response times relative to the number of Vusers running at any given point during the load test. This graph helps you view the general impact of Vuser load on performance time and is most useful when analyzing a load test which is run with a gradual load. Title: Graph Type: Base Graph: Additional: Granularity: Transaction Response Time Under Load Correlate Running Vusers Average Transaction Response Time 1 Second

Color

Scale 1 1 1

Measurement Action_Transaction vuser_end_Transaction vuser_init_Transaction

Min. 11.613 0.0 0.002

Ave. 12.37 0.0 0.002

Max. 13.095 0.0 0.002

SD 0.352 0.0 0.0

4. Hits Per Second

Displays the number of hits made on the Web server by Vusers during each second of the load test. This graph helps you evaluate the amount of load Vusers generate, in terms of the number of hits. Title: Current Results: Filters: Group By: Granularity: Hits per Second C:\Documents and Settings\loadrunner\Local Setting s\Temp\res\res.lrr None 16 Seconds

Color

Scale 1

Measurement Hits

Graph Min. 1.875

Ave. 3.066

Graph Max. 6.375

Graph Median 2.438

Graph SD 1.266

5. Vuser Load Scheme

Displays the number of Vusers that executed Vuser scripts, and their status, during each second of a load test. This graph is useful for determining the Vuser load on your server at any given moment. Title: Current Results: Filters: Group By: Granularity: Running Vusers C:\Documents and Settings\loadrunner\Local Setting s\Temp\res\res.lrr Vuser Status = (Run) 16 Seconds

Color

Scale 1

Measurement Run

Graph Min. 0.0

Graph Ave. 0.75

Graph Max. 2

Graph Median 1

Graph SD 0.829

6. Transaction Response Times

Displays the average time taken to perform transactions during each second of the load test. This graph helps you determine whether the performance of the server is within acceptable minimum and maximum transaction performance time ranges defined for your system. Title: Current Results: Filters: Group By: Granularity: Average Transaction Response Time C:\Documents and Settings\loadrunner\Local Setting s\Temp\res\res.lrr Transaction End Status = (Pass), (Include Think Ti me) 16 Seconds

Color

Scale 1 1 1

Measurement Action_Transaction vuser_end_Transaction vuser_init_Transaction

Min. 11.613 0.0 0.002

Ave. 12.37 0.0 0.002

Max. 13.095 0.0 0.002

SD 0.352 0.0 0.0

10

7. Terminology
7.1. LoadRunner Objects
Term Vuser Scripts Load Test Definition A Vuser script describes the actions that a Vuser performs during the scenario. Each Vuser executes a Vuser script during a scenario run. The Vuser scripts include functions that measure and record the performance of your applications components. Tests a system's ability to handle a heavy workload. A load test simulates multiple transactions or users interacting with the computer at the same time and provides reports on response times and system behavior. Run-Time settings allow you to customize the way a Vuser script is executed. You configure the run-time settings from the Controller or VuGen before running a scenario. You can view information about the Vuser groups and scripts that were run in each scenario, as well as the run-time settings for each script in a scenario, in the Scenario Run-Time Settings dialog box. A scenario defines the events that occur during each testing session. For example, a scenario defines and controls the number of users to emulate, the actions that they perform, and the machines on which they run their emulations. The Schedule Builder allows you to set the time that the scenario will start running, the duration time of the scenario or of the Vuser groups within the scenario, and to gradually run and stop the Vusers within the scenario or within a Vuser group. It also allows you to set the load behavior of Vusers in a scenario. When you work with the Analysis utility, you work within a session. An Analysis session contains at least one set of scenario results (lrr file). The Analysis utility processes the scenario result information and generates graphs and reports. The Analysis stores the display information and layout settings for the active graphs in a file with an .lra extension. Each session has a session name, result file name, database name, directory path, and type. A transaction represents an action or a set of actions used to measure the performance of the server. You define transactions within your Vuser script by enclosing the appropriate sections of the script with start and end transaction statement. Vusers or virtual users are used by LoadRunner as a replacement for human users. When you run a scenario, Vusers emulate the actions of human users working with your application. A scenario can contain tens, hundreds, or even thousands of Vusers running concurrently on a single workstation.

Run-Time Settings

Scenario

Scheduler

Session

Transactions

Vusers

7.2. Graph Information

Term Average Hits Maximum Measurement Median Minimum Network Delay Network Path Response time Scale (or granularity) Standard Deviation (SD) Throughput Vuser Load Definition Average value of the graph measurement's. The number of HTTP requests made by Vusers to the Web server. Maximum value of the graph measurement's. This is the type of resource being monitored Middle value of the graph measurement's. Minimum value of the graph measurement's. The time it takes for a packet of data sent across the network to go to the requested node and return. The Network Path is the route data travels between the source machine and the destination machine. The time taken to perform a transaction. In order to display all the measurements on a single graph, thus making the graphs easier to read and analyze, you can change the scale or (granularity) of the x-axis. You can either set measurement scales manually, view measurement trends for all measurements in the graph, or let Analysis scale them automatically. The Legend tab indicates the scale factor for each resource. The square root of the arithmetic mean value of the squares of the deviations from the arithmetic mean. Throughput is measured in bytes and represents the amount of data that the Vusers received from the server. When you run a scenario, the Vusers generate load or stress on the server. LoadRunner monitors the effect of this load on the performance of your application.