Average Response times (319 Views)
Reply
Occasional Contributor
satishh107
Posts: 8
Registered: ‎06-12-2013
Message 1 of 4 (319 Views)
Accepted Solution

Average Response times

When i perform log in task on application,  it takes about 2-3 seconds but when i perform the same scenario in loadrunner tool, it gives average response of more than 10 seconds?

 

Also while running above scenario multiple times, it has been noticed Average Response Time given by loadrunner is not always consistent. Sometimes it would be 10 seconds and for other run it would be 7 seconds.

 

Appreciate your quick reply.

 

Thanks,

Satish

HP Expert
Editus
Posts: 650
Registered: ‎04-06-2011
Message 2 of 4 (295 Views)

Re: Average Response times

Hello

This is actually expected, when you run a loadtest the response time is expected to be higher, it depends on how much load the server is taking and how powerfull it is, but also notice this is an average, not the time for each en everysingle vuser, so let say you ran 10 vusers, and all of them nedeed 2 seconds to complete this transaction, but 2 of them needed 10 seconds and one more needed 20 seconds, so the reported average will be 5.4 seconds,  the less vusers you run the higher the impact in average, you should check the 90 percentile to get a better idea of what is going on with most of vusers.

 

 

hope this helps

 

regards

Occasional Visitor
vijay141
Posts: 2
Registered: ‎04-21-2014
Message 3 of 4 (232 Views)

Loadrunner truClient transaction time breakdown

I am new to loadrunner.I have created scripts using truclient protocol.How to get breakdown transaction time in Analysis.
Frequent Advisor
ssawale
Posts: 42
Registered: ‎07-16-2010
Message 4 of 4 (219 Views)

Re: Loadrunner truClient transaction time breakdown

[ Edited ]

Yes, its very hard even for people to understand and consume when you do load test things are different than a single user test and even you can't repro such situations by few users exercising work-flows manually. Its all about timing... if you do things slowly server has breathing time to process and response and if you do too fast you see things get queued that affect response.

 

When you finish your test. You can filter think time and also see raw values in Loadrunner analysis to get better idea as which users and what iterations are slow.  If transaction has more number of steps then you can break it down further to find the slower action causing issues during load. In case of TruClient also don't forget to use Truclient functions such as Utils.addAutoFilter(...) , Utils.removeAutoFilter(..., ... ) to avoid calls to external sites like facebook, twitter , googleapis, etc.  if they aren't relevant to make your functionality work and cause extra non-predictive delays.

 

I hope it helps!

 

Thanks!

The opinions expressed above are the personal opinions of the authors, not of HP. By using this site, you accept the Terms of Use and Rules of Participation.