Answer Posted / avilineni

If you find any bottleneck first we need to figure out whether it is related to application , environment or within a testing tool.

1. First step to check the testing tool if load generaters are generating load , no of active users are same as actual load , no errors in the script. If this is fine and no issues observed . Next go to second check

2. Check if the environment is up and running fine with no issues.
3. Next check the servers for any error logs in error logs, system output messages. If no errors are seen further drill down and follow bottom top approach to isolate the issue
4. Check Database for any errors , slow running queries , and system utilization if any suspicious is observed make a note of it.
5. Next check application server using any monitoring tool for heap memory , response times , Garbage collection and CPU. If any transaction response time seems to be high further drill down to method level to check the layer causing slowness
6. raise a issue in ticketing tool and assign to development team with all the analysis and talk to manager from Testing team and provide him the snapshot of it.

How vugen create a vuser script?

1112

---

How does loadrunner execute a performance scenario?

1172

---

How load runner interacts with the application?

1507

---

What are monitors?

1115

---

How to identify what to correlate and what to parameterize?

1096

---

What is the advantage of using loadrunner?

1141

---

What is the load runner testing process?

1362

---

What are the information contain by script windows for each script in the list?

1178

---

What is the use lr_abort function?

1352

---

What is vugen recording and scripting?

1193

---

What do you mean by creating vuser script?

1164

---

How can we edit the vuser script?

1120

---

What is script list?

1317

---

Difference b/w 9.1 and 9.5 Versions in LoadRunner?

7536

---

Which components have you used in loadrunner ?

1069

---