High response times from load runner with TruClient protocol , not from the browser during single us
High response times from load runner with TruClient protocol , not from the browser during single user run through LAN. Some of the transactions are having low response time on loadrunner TruClient compare to Browser manual single user Run.
1. We checked with single user on browser through LAN (calculated the time through stopwatch) some of the transacations are taking 1 second. where as in loadrunner single user run it is taking 0.012 seconds in oncase.
2. in second case some of the transactions are taking 1 second where as loadrunner single user run it is showing 4 seconds response time.
fnally response times are not mattched. can anybody explain the reason for this ?
Re: High response times from load runner with TruClient protocol , not from the browser during singl
I had the same problem with an application registered with TruClient protocol: times were too fast compared to the real web browsing. I wrote in the forum and one suggestion were to change the end event in the interested step, where there's the time problem. In my case, this option didn't help but maybe can resolve your problem.
Below, the link to the post I've sent to the forum with a list of possible solutions:
In my personal opinion, this curious behavior depends on the "communication" between LoadRunner and the application itself.
Hope to help,