Mercury load runner

CONTENTS
What is Performance Testing?
Introducing Mercury LoadRunner
LoadRunner Terminology
Mercury LoadRunner Components
Steps in LoadRunner Testing Process
LoadRunner Virtual User Generator
Mercury LoadRunner Controller
Mercury LoadRunner Analysis

What is Performance Testing?


Performance testing focuses on the volume, load,
scalability and stability of the underlying software
architecture and hardware in real-time environments. This
includes the various software components software and
application servers, hardware servers and network
components that make up today's complex software
systems.

3

Introducing Mercury LoadRunner

 LoadRunner is a tool used to emulate an environment

where multiple users work concurrently. While the
application is under load, LoadRunner accurately
measures and analyzes the system performance, and its
functionality

LoadRunner Terminology
Scenarios
Using LoadRunner, you divide your application performance testing
requirements into scenarios.
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.
Vusers
In the scenario, LoadRunner replaces human users with virtual users
or Vusers.
When you run a scenario, Vusers emulate the actions of human users
—submitting input to the server.
A scenario can contain tens, hundreds, or even thousands of Vusers.

Vuser Scripts
The actions that a Vuser performs during the scenario are described
in a Vuser script.
When you run a scenario, each Vuser executes a Vuser script. The
Vuser scripts include functions that measure and record the
performance of the server during the scenario.
Transactions
To measure the performance of the server, you define transactions.
Transactions measure the time that it takes for the server to respond
to tasks submitted by Vusers.

Rendezvous Points
You insert rendezvous points into Vuser scripts to emulate heavy user
load on the server.
Rendezvous points instruct multiple Vusers to perform tasks at
exactly the same time.
For example, to emulate peak load on the bank server, you insert a
rendezvous point to instruct 100 Vusers to simultaneously deposit
cash into their accounts.
Controller
You use the LoadRunner Controller to manage and maintain your
scenarios.
Using the Controller, you control all the Vusers in a scenario from a
single workstation.

Hosts
When you execute a scenario, the LoadRunner Controller distributes
each Vuser in the scenario to a host.
The host is the machine that executes the Vuser script, enabling the
Vuser to emulate the actions of a human user.
Performance Analysis
Vuser scripts include functions that measure and record system
performance during load-testing sessions.
During a scenario run, you can monitor the network and server
resources.
Following a scenario run, you can view performance analysis data in
reports and graphs.

Mercury LoadRunner Components
 Virtual User Generator (VuGen)
 LoadRunner Controller
 LoadRunner Analysis

Steps in LoadRunner Testing Process
Plan the test

 Plan the test
 Create Vuser scripts
 Create controller scenario

Create Vuser Scripts

Create Controller Scenario

 Run the scenario
 Monitor the scenario

Run the Scenario

 Analyze the results
Monitor the scenario

Analyze the results

LoadRunner Virtual User Generator
VuGen Code View

VuGen Script
Editor

Logs

Section of Script
Vuser_init
Action
Vuser_end

Sections

Developing Vuser Scripts
Walk through the scenario to be
scripted
Record the scenario
Edit or enhance the script
Configure the runtime settings
Run the Vuser script
Re-enhance and re-run till working
properly
Incorporate the script into LR scenario

Scripting
Mainly ‘C’ Programming Language Based
Able to incorporate ‘C’ looping structures (for, if, while,…)
Can also use Java, JavaScript, VB and VBScript

Script Enhancements
Transactions
Parameterization
Rendezvous Points
Think Time

Defining User Behavior
Recording Options






Recording
Browser
Recording Proxy
Advanced
Correlation

Runtime Settings
 General
 Network
 Browser
 Internet Protocol

Mercury LoadRunner Controller

New Scenario:
Manual Scenario
Percentages Option
Goal Oriented Scenario

Controller Design Tab

Scenario Schedule
Section (Manual
Scenario)
Edit Schedule
Scenario

Scenario Group
Section (Manual
Scenario)

Run Tab

Configurations on Design Tab
Edit Schedule
Setting Up the Rendezvous (If Any)
Runtime Settings
Load Generators
No of Vuser per Script

Controller Run Tab

Scenario Status
Scenario Groups
Available Graphs Tree
Graph Viewing
area
Online Monitor
Graphs

Graph Legend

Monitoring at Scenario Run
In Scenario Status you can monitor the errors and
number of transactions done.
In Scenario Groups you can monitor what any
particular group of users are doing.
You can monitor the different graphs In the graph
viewing area.
Legends area will have whatever measurements that
you have added and what color on the graph
represents each measurement.

Mercury LoadRunner Analysis
Analysis Summary

Available Graphs

Summary Report

Data with Legend

Viewing a part of scenario
You can instruct LoadRunner to calculate graphs and
reports based on a part of the scenario.
For example, if you have a scenario with a duration of
400 seconds, but you are only interested in the period
beginning at 60 and ending with 360 seconds, you can
specify that interval in the Time Filter dialog box.
After setting the time filter, you must rebuild the
result database in order for the changes to take effect.

Merging Graph

Running Virtual Users
Graph
The Running Virtual User
graph displays the number of
Vusers that executed Vuser
scripts during each second of
a scenario run. This graph is
useful for determining the
Vuser load on your server at
any given moment. The x-axis
represents the elapsed time
(in seconds) since the start of
the scenario run. The y-axis
represents the number of
running Vusers in the
scenario

Transactions per
Second Graph
(Passed)
The Transactions per
Second (Passed) graph
displays the number of
completed,
successful
transactions performed
during each second of a
scenario run.

About Scenario Performance
During scenario execution, Vusers generate data as

they perform their transactions.
LoadRunner allows you to generate graphs that show
scenario activity or overall scenario performance.
Scenario performance graphs and reports let you
analyze Vuser behavior throughout the scenario.
The Performance graphs map the transaction
response time, and other general information about
the scenario.

Transaction
Response Time
(Percentile)
The Percentile graph
analyzes
the
percentage
of
transactions
that
were
performed
within a given time
range. This graph
helps you determine
the percentage of
transactions
that

Transaction
Response Time
Under Load
Graph
The
Transaction
Response
Time
Under Load graph
indicates transaction
response
times
relative
to
the
number of Vusers
running at any given
point during the
scenario.


Hits Per Second
Graph
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

Throughput
Displays the amount of
throughput (in bytes)
on the Web server
during the load test.
Throughput represents
the amount of data that
the Vusers received
from the server at any
given second. This
graph helps you to
evaluate the amount of
load Vusers generate,
in terms of server


Server and
Network Graph(s)
Depending
on
the
measurements selected
and the server selected
LoadRunner produces
graphs based on them.
Sample: Weblogic and
Oracle

Mercury
LoadRunner

Thank You!

Mercury load runner

Recommended

Recommended

More Related Content

Similar to Mercury load runner

Similar to Mercury load runner (20)

Recently uploaded

Recently uploaded (20)

Mercury load runner