| || |
- 1 Post By Yogi_Shukla
- 1 Post By jpulley3
Pacing in Load Runner.
To execute a particular script with 50 users for a duration of 1 hour and only 100 transactions should be executed. Now what should be pacing value to execute only 100 transactions....
Note: Test should only be controlled by pacing...
seems like an interview question ...its very easy dude and requires only simple maths to calculate...
pacing is time interval between the iterations. so you can calculate to find out in your scenario.
Yep, an interview question. Think it through. This is a foundation skills question, independent of performance testing tool.
By the way, companies do monitor this forum for people disclosing take home questions or in interview questions, so you may have just "marked" yourself.
I think if this is the case then thread should moved to Interview forum.
Its one of my client requirement. During the load test all other scenarios need to be executed as per the user distribution, but for one of the specific scenario, it need to be executed on transaction basis. Now the steady state of the test is 1 hour so during that 1 hour only 100 transactions should be executed. My concern is as the users load increase during ramp up the transaction response time will also increase, due to which i am not able to calculate the right pacing to be used for this scenario. Do let me know if anyone have any suggestion.
Read through fixed intervel pacing in run time settings.
I have not used LR for a long time so this may not make much sense.
What if you make 5 separate runs that start one after the other.
Maybe the first has only 5 users, then 15. Maybe the last has 30. Well something that adds up to 100.
If you were in performance testing for long you will see almost every client has this requirement and if they not, you have to propose yourself as they can be unaware of this criteria and its your responsibility as Perf Test engineer to give them the best.
Its one of my client requirement.
To calculate the pacing time we see the whole flow rather than only one transaction.
My concern is as the users load increase during ramp up the transaction response time will also increase, due to which i am not able to calculate the right pacing to be used for this scenario.
And of course dude, you have to take the buffer time in consideration as well in case response time increases exceptionally.