What is the Architecture of LoadRunner?
The architecture of LoadRunner is a little complex. Still, you can understand when you read it thoroughly. Consider an example where you have given a task to check the performance of 5K users for Amazon.com. It is not necessary that 5000 users have to be analyzed for Home Page only, but they can exist on different pages of the website. So, what is the process of simulating differently?
VUGen
VUGEN or Virtual USER Generator is an IDE that allows replication of behavior of system under load. it supports the recording feature where communications can be recorded or utilized as a recorded script. the other name for this recorded script is VU or Virtual User Script. here is a list of processes that can be stimulated using VUGen.
- Checkout
- Payment Processing
- Check the product page
- Check the MyAccount Page
Controller
Once the virtual user script is final, the controller is the major component that takes care of load simulation. Here are a few examples for your reference:
- There are how many virtual users against each business group, and the same is true for virtual groups as well?
- What is the behavior of virtual users?
- What is the nature of Load Scenarios?
- What injectors to be used, and there are how many virtual users against each injector?
- How to collate outputs periodically?
- What is IP spoofing, error reporting, and transaction reporting, etc.?
Take an analogy to make things clear:
- There are 750 users in checkout.
- 500 users are processing payments.
- A total of 3500 users are surfing the product page.
- There are 250 users at the MyAccount page.
This is a simple scenario; let us make it a little more complex for you:
- Initiate 3500 users every 2 seconds till a load of 3500 users at the product page.
- Now, iterate for 30 minutes.
- Suspend the iteration for 24 virtual users.
- Re-start 20 virtual users.
- Initiate 2 virtual users for Checkout, payment processing, and My Account page every second.
- Generate 2500 virtual users at machine A.
- Generate 2500 virtual users at machine B.