Load Runner Tips: Creating new scenario, creating load runner scenario, ramp up ramp down in scenario, adding virtual user in scenario, adding load generator in scenario, adding graph in controller, design load runner scenario, goal oriented scenario, manual scenario, ,Performance testing, load testing, stress testing, soak testing, endurances testing tool

Controller Home

Controller is main component of load runner which is used to create load testing scenario. Below are the key attribute to deign Load testing scenario:

User Load- Total no user load that need to generated on web server
Load Generators – LG are the machine from where actual user load is generated, you can use multiple LG in one test and these LG can be in multiple geography location to major latency.
Think Time- Controller can be used to redefine think time used in script. It can be random, percentage etc.
Pacing- Controller can be used to redefine pacing used in script. It can be random, percentage etc.
User Ramp up- To define how virtual user load will ramp up on web servers e.g 1user every 5 sec etc
User Ramp Down- To define how virtual user load will ramp down on web servers e.g 1user every 5 sec etc
Load Test Duration- duration of load test to run after all virtual users are ramp up on web servers.

There are two types of scenarios:

Goal oriented scenario: In goal oriented scenario one must define the goal that application want to achieve to pass the load testing e.g pass no of transaction, hits par second, no of user load etc
Manual scenario: In manual scenario we define the all the parameter for load test and run the load test until we manually not satisfy with the performances of the application

Graphs and MonitorController allows monitoring multiple webserver and multiple graphs during load testing, below are the communally used graph in controller:

Client Side monitors: Hits Per second, HTTP Responses Per second, Pages downloaded per second, Throughput, AVG Transaction response time, Transaction per second (Pass), Transaction per second (Failed), Running Virtual Status, Web Transaction Break Down, Error Per Second etc.
Server Side Monitor: NT/UNIX/Linux monitors (Provide hardware, network and operating system performance metrics such as CPU Memory and network throughput),
Data base server resource monitors: Provides performance data inside the database such as active Database connections

State of Virtual User:While running Load test in controller virtual user will go from 12 states which are

Down
Pending
Init
Ready
Run
Rendezvous
Passed
Fail
Error
Gradually Exiting
Exiting
Stopped

Controller Component: There are two components in controller which are:

Generator (LG): 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). There are two types of LG in Controller Local host and Remote host. If you are using controller as load generator then that is called local host. If you are using LG other thane controller machine than that is called as Remote host, you can use multiple remote host LG but only one Local host LG.
Configuration of LG Machines:
250 USER LOAD
1) Processor (Dual core)
2) Hard disk 80 GB
3) RAM 1GB OR ABOVE
500 USER LOAD
1) Processor: (Dual core)
2) Hard disk: 80GB
3) RAM: 2GB OR above
1000 User load
1) Processor: 4 CPU boxes (two dual core processor)
2) Hard disk: 120 GB
3) RAM:-4GB OR ABOVE
Agent ProcessIt establishes communication between the load generator and load controller. Exe of agent Preprocess: - magnetproc.exe (Magentproc->mercury agent process)


	Controller Home Controller is main component of load runner which is used to create load testing scenario. Below are the key attribute to deign Load testing scenario: User Load- Total no user load that need to generated on web server Load Generators – LG are the machine from where actual user load is generated, you can use multiple LG in one test and these LG can be in multiple geography location to major latency. Think Time- Controller can be used to redefine think time used in script. It can be random, percentage etc. Pacing- Controller can be used to redefine pacing used in script. It can be random, percentage etc. User Ramp up- To define how virtual user load will ramp up on web servers e.g 1user every 5 sec etc User Ramp Down- To define how virtual user load will ramp down on web servers e.g 1user every 5 sec etc Load Test Duration- duration of load test to run after all virtual users are ramp up on web servers. There are two types of scenarios: Goal oriented scenario: In goal oriented scenario one must define the goal that application want to achieve to pass the load testing e.g pass no of transaction, hits par second, no of user load etc Manual scenario: In manual scenario we define the all the parameter for load test and run the load test until we manually not satisfy with the performances of the application Graphs and MonitorController allows monitoring multiple webserver and multiple graphs during load testing, below are the communally used graph in controller: Client Side monitors: Hits Per second, HTTP Responses Per second, Pages downloaded per second, Throughput, AVG Transaction response time, Transaction per second (Pass), Transaction per second (Failed), Running Virtual Status, Web Transaction Break Down, Error Per Second etc. Server Side Monitor: NT/UNIX/Linux monitors (Provide hardware, network and operating system performance metrics such as CPU Memory and network throughput), Data base server resource monitors: Provides performance data inside the database such as active Database connections State of Virtual User:While running Load test in controller virtual user will go from 12 states which are Down Pending Init Ready Run Rendezvous Passed Fail Error Gradually Exiting Exiting Stopped Controller Component: There are two components in controller which are: Generator (LG): 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). There are two types of LG in Controller Local host and Remote host. If you are using controller as load generator then that is called local host. If you are using LG other thane controller machine than that is called as Remote host, you can use multiple remote host LG but only one Local host LG. Configuration of LG Machines: 250 USER LOAD 1) Processor (Dual core) 2) Hard disk 80 GB 3) RAM 1GB OR ABOVE 500 USER LOAD 1) Processor: (Dual core) 2) Hard disk: 80GB 3) RAM: 2GB OR above 1000 User load 1) Processor: 4 CPU boxes (two dual core processor) 2) Hard disk: 120 GB 3) RAM:-4GB OR ABOVE Agent ProcessIt establishes communication between the load generator and load controller. Exe of agent Preprocess: - magnetproc.exe (Magentproc->mercury agent process)
	FIND MORE ON LOAD RUNNER TIPS \| About Load Runner \| Creating scripts in Load Runner \| Load Runner scenario \| LR Analysis \| Performance Tuning \| Performance Testing \| LR Errors \| Interview Question \| Load Runner Tool \| Correlation Practice \| Site Map \|