Professional Documents
Culture Documents
Load Runner Data
Load Runner Data
sired performance objectives; these performance objectives are often specified in a service level agreement
(SLA). A load test enables you to measure response times, throughput rates, and resource-utilization
levels, and to identify your application’s breaking point, assuming that the breaking point occurs below
the peak load condition.
purpose:To verify application behavior under normal and peak load conditions.
Stress testing – involves testing an application under extreme workloads to see how it handles high
traffic or data processing .The objective is to identify breaking point of an application
Purpose:To determine or validate an application’s behavior when it is pushed beyond normal or peak
load conditions.
Endurance testing – is done to make sure the software can handle the expected load over a long period
of time.
Spike testing – tests the software’s reaction to sudden large spikes in the load generated by users
Identify your testing environment – Know your physical test environment, production environment
and what testing tools are available. Understand details of the hardware, software and network
configurations used during testing before you begin the testing process. It will help testers create more
efficient tests. It will also help identify possible challenges that testers may encounter during the
performance testing procedures.
Identify the performance acceptance criteria – This includes goals and constraints for throughput,
response times and resource allocation. It is also necessary to identify project success criteria outside of
these goals and constraints. Testers should be empowered to set performance criteria and goals because
often the project specifications will not include a wide enough variety of performance benchmarks.
Sometimes there may be none at all. When possible finding a similar application to compare to is a good
way to set performance goals.
Plan & design performance tests – Determine how usage is likely to vary amongst end users and
identify key scenarios to test for all possible use cases. It is necessary to simulate a variety of end users,
plan performance test data and outline what metrics will be gathered.
Configuring the test environment – Prepare the testing environment before execution. Also, arrange
tools and other resources.
Load runner Controller material
what is load runner controller ?
Controller is manage and maintain the scenario . using controller you control all the vuser in single work
station .
Installation of L.R
1. Exe-(Here controller & Load generator both are in same place)
2. Service-(Here only LG is present. LG is here service purpose to controller)
.
Script runtime settings Scenario Runtime settings
Load generator lo script create Load controller lo scenario design
chesetappudu (Vugen) chese runtime chesetappudu chese runtime setting
settings
Eedhi script generate chesetappudu Edhi controller lo unte runtime settings
Vugen lo chese runtime setting LC lo runtime settings options motham
LG lo script aye runtime settings okke vidhamgaa unteene script aneedhi
options correct ga run authundhi
Load Controller lo ye modifications chesina I mean ye operations chesina save cheyali appude aa changes
apply avuthayi
Load generator/ Load controller (to generate load we use load generators)
Requests two types
1. Local request (coming from working computer)
2. Remote request (coming from another location)
Load generator: - It generates the user loads to the controller by using agent process.
Load generator is internal component of load controller
Exe of load generator: - MDRV.exe
MDRV (Mercury driver virtual)
It is a driver program given by mercury
Agent Process: - It establishes communication between the load generator and load controller.
Exe of agent Preprocess: - magnetproc.exe
Magentproc->mercury agent process
Load Generator: - To generate the number of Vusers wile running the scenario in load controller by
using agent process
Or
It generates the user loads, two types of load generator are there.
Local host: - if we use the load generator as controller machine then that is called as local host.
Or
Use the load generator in the controller machine is called local host
Remote host: - : if we use the load generator other than the controller machine, than that is called
remote host.
Or
Other then the controller machine is called remote host as a load generator
Controller:
This component uses for running the multi user business scenarios.
Controller Scenario:
Lr has two types of scenarios.
1. Manual Scenario,
2. Goal Oriented Scenario
1. Manual Scenario:
Create the controller scenario based on the no of uses.
List of options available under manual scenario.
Load Generator, Group Name and Result Directory.
Goal Types:
1. Virtual users,
2. Hits/second,
3. Transaction per second,
4. Transaction Response time & pages per minutes.
1. Virtual Users: Define the no of uses to run under goal oriented scenario.
3. Transaction per second: To set the no of transactions passed of the server per second.
4. Transaction Response time: To set the time taken by the server to process to our request.
Depends on the acceptable response time criteria you can set this goal.
Note: - Each group can be assigned a different script to emulate different business process
Scenario Building:
1. Scheduling by Scenario: To run all the scripts at the same time in the load controller. We can use
this option.
2. Schedule by Group: To run the scenario in group wise, we can use this option.
Scenario Start Times: To start the scenario execution automatically without the user interaction.
Schedule Builders:
Ramp Up: To set the time for initializing the v users.
Load all v users simultaneously.
Start no of users every time
Duration: To set the time duration to run all the v users.
Run until completion
Run for (Duration)
Run indefinitely.
Ramp Down: To down the v users from the run status.
Stop all v users simultaneously.
Stop one user for every time.
IP spoofing:
To allocate the IP address for each vuser we can use IP spoofing
Navigation:
Create the multy IP address using IP wizard in Load Runner tools (not in Vugen tools) in installation
tools. Go to scenarios in load controller
Enable IP spoofer (eekada IP address annedhi each user ki allocate avuthundhi)
Counters:
Data Base: Cache hit ratio, I/O batch writes per second, Lazy writes per second &
Out standing records.
Monitoring:
Keep watching the data on the server in controller
Monitoring done 2 ways
1 controller
2. Run -> Perfmon
MONITORS:-
Load Runner offers wide range of performance monitors for isolating bottlenecks
Monitors display real time data during testing
Note: - you can display up to 16 online monitors at a time
Server Monitors:-
NT/UNIX/Linux monitors
Provide hardware, network and operating system performance metrics such as CPU
Memory and network throughput
NT server resources
Unix/Linux server monitors
Note:-
Performance monitors are licensed by the load runner controller
A monitor cannot be configured unless the license has been purchased
To find out which monitors your current license allows
Bottleneck: It is a pinpoint or breaking point where the server will get up gration and degration. (Up
and down in graph)
Tuning:
It is an area to find out the bottlenecks in different areas.
Bottleneck may be: Application, application server, Data base server, Network and web server.
How did you plan the load? What are the criteria?
There are two types of documents available for carrying performance testing.
Task Distillation Management: Enter the P T application is divided into unit modules and is
distributed over the terms. TL/PM is responsible for dividing the modules test engineers. It is also known
as licensed agreements.
Task Profiler: It maintains the no of transaction under tasks.
Filters:-
Filters let you display only a specific transaction status, transaction name, group, vuser
Def: - “To get the data based on our specified condition”.
What is filter?
To get the data based on our specified condition. You can set the filter for user id condition elapsed
scenario condition graph represented data.
You can set the filters for user id condition, elapsed scenario condition, graph represented data
What is granularity?
To set the time gap between two salvation points, we can use.