CODEWITHSUNDEEP
htmlhttpanalysisloadrunnertruclient
Jacson
Jacson

Reputation: 143

LoadRunner Truclient vs protocol Http/Html

i'll try to compare the same script done in Http/html with TruClient. In both of the scenarios, it has same think time/wait time, same number of vusers, same pacing.

Is it possible that they have approximately same time for each transactions but they are so different in term of total number of passed transactions?

Ty in advance

Upvotes: 0

Views: 8422

Answers (2)

James Pulley
James Pulley

Reputation: 5692

The question comes on what are you trying to measure? Are you trying to measure the response time of your servers or are you trying to measure the weight of the client in the impact of response time? I put forward the hypothesis that it is possible to measure the client weight by examination of the times captured with the developer tools in both development and also in functional testing.

So much of this client weight is related to page architecture that if you are waiting for performance testing to show you that your page architecture is problematic then you likely will not have time to fix the issues and retest before going to production.

I also recommend the collected O'Reilly works of Steve Souders which will help to bring home the client bound concepts for page design and how much this impacts the end user experience over and above how fast the server responds.

http://www.oreilly.com/pub/au/2951

Upvotes: 0

sivaramaraju
sivaramaraju

Reputation: 340

In web HTTP/HTMl protocol, Response time = Processing time + Latency (time taken by network while transferring data).
In Truclient protocol, Response time = Processing time + Latency + Rendering time

Hence you will found a difference between both response times.

And execution times will differ in both protocols, hence total number of passed transactions also vary.

Upvotes: 1

Related Questions