Controller

CONTROLLER

Note: Controller extension is “.lrs”.

Manual scenario: Manually we have to design the scenario by providing ramp up, ramp down, duration, number of users to generate the anticipated load against the application.

Percentage mode: It will distribute the load in between use cases in terms of percentage.

Goal oriented scenario: Controller itself will design the scenario as per the goal.
 Controller having 3tabs:
1. Design tab.
2. Run tab.
3. Diagnostics tab.
1. Design tab: where you can design the scenario.
Note: scenario extension is “.lrs”.

 Ramp up: gradually increasing the load against application.

 Duration: indicates test duration which extends ramp up and ramp down time. this is called “duration”, ”standalone”, ”steady time”.

 Ramp down: gradually reducing load from application.

 Elapsed time: this is the test duration time which includes ramp up, steady time, ramp down.

 Throughput: bits received from server.

 Hits per second: per second how many hits happening.

 Schedule by scenario: it considers all the scripts like a scenario and configure ramp up, ramp down, duration.
 (or)
Consider as a scenario by sharing ramp up, ramp down, duration.

 Schedule by group: every script consider as a different scenario by having their own
ramp up, ramp down, duration.

 Real world schedule: allow you to create multiple actions (ramp up, ramp down,
duration).

 Basic schedule: you have only basic action under this option (one ramp up, one ramp
down).

2. Run tab:
 User status:
Down
Pending
Initialization
Ready
Run
Rendezvous
Passed
Failed
Error
Gradual exiting
Exiting
Stopped

 Gradual exiting: whenever test duration completed by the time user are in mid of
iteration. So those users will be moved to gradual exiting once the iteration is finished users will be come out from test.
Note: elapsed time stats whenever you hit the start button.

3. Diagnostics tab: By default web page diagnostics are available at free of cost. We have to buy license for java, Siebel, sap, oracle etc.

Manual scenario:
 Check list:
1. Choose manual scenario.
2. Push the script into controller.
3. Choose schedule by scenario (or) schedule by group.
4. Choose real world (or) basic schedule.
5. Assign the quantity.
6. Assign load generators.
7. Verify connectivity with LG’s.
8. Configure SLA’s (if required).
9. Configure runtimes settings for every script.
10. Set the result path.
11. Provide ramp up, ramp down, duration.

Note: whenever situations demands like every script should run for multiple durations with vary ramp up’s then you can choose schedule by group.

Differences between request and hit:
User action is a request.
Successful request is a hit.
Note:One request may contains multiple hits.



 Goal oriented scenario: controller itself will design the scenario according to goal.
 Check list:
1. Choose goal oriented scenario.
2. Push the scripts into controller.
3. Click on edit scenario goal.
4. Provide profile name.
5. Provide goal type and threshold point.
6. Provide max and min users.
7. Provide duration once it reaches the goal.
8. Configure notifications if it is not able to reach goal.
9. Distribute load in terms of percentage.
10. Assign LG and check the connectivity.
11. Configure SLA’s (if required).
12. Set the result path.

Note: Goal types
1. Virtual users.
2. Transaction per second.
3. Hits per second.
4. Response time.
5. Pages per minute.

IP Spoofing:
Masking the original IP address and using the different IP address is called IP spoofing.Whenever load balancer is not functioning. Due to the request source of IP address. We
have to mask the original IP address and mask sure that every user has to use different IP address.
Process: In realistic environment every end users using different IP address to access the application but in LR environment all the users are invoking from same LG and same IP which is not realistic.
Step1:Request IT infrastructure guys to provide dynamic IP address.
Step2: Ask them to configure these IP address in DHCP server.
Step3: We have to configure these IP address in load generator using IP wizard option.
Step4: Enable IP spoofing option in controller.

Load balancing: Load balancer is a URL, which will distribute load in between web instances.
As part of performance testing you will receive two kinds of URL.
1. Direct URL: It will access web instance directly.
2. Load balancer URL: which will distribute the load in between web instances.
We do have two types of load balancer
1. Hardware load balancer
2. Software load balancer
Among the above, hardware load balancer is accurate and good
Load balancer URL will distribute the load based on below algorithms.
1. IP sticky
2. Least connections
3. Round robin
4. Round passion
5. Least load