Analysis and calculation of throughput (throughput) in LoadRunner

Analysis and calculation of throughput (throughput) in LoadRunner

Core tips: Throughput translation for throughput, according to the general understanding of network throughput expressed in the unit time through the amount of network card data

Throughput translation for throughput, according to the general understanding of network throughput in the unit time through the amount of data network card, including the local network card sent out the amount of data also includes the local network card received the amount of data, But this understanding is wrong in the throughput of LoadRunner Records!
First, the correct results are presented, and then the specific tests are used to prove that:

The throughput of the LoadRunner record is the sum of all bytes received by the server, regardless of the number of bytes sent locally!

　　We do an experiment with baidu.com, and the process is simple:

1, using Vugen record Baidu's homepage, only open the homepage can

2, in the recording log to record the client and server-side data transmission situation, the total number of bytes emitted and the total number of bytes received.

Recording log content is as follows:

Request connection:remote Server @ 220.181.6.19:80 (service=) (sid= 1) proxied!

"GET/"

(sid:1) Client--server:407 bytes (service=http)

(sid:1) Server, client:208 bytes (service=http)

(sid:1) Server, client:1990 bytes (service=http)

"Get/img/baidu_logo.gif"

(sid:1) Client--server:457 bytes (service=http)

(sid:1) Server, client:1779 bytes (service=http)

Address lookup for test75 = 10.10.10.1

Request connection:remote Server @ 220.181.5.21:80 (service=) (sid= 2) proxied!

"Get/img/gs.gif"

(sid:2) Client--server:450 bytes (service=http)

"Get/js/bdsug.js?v=1.0.1.0"

(sid:1) Client--server:460 bytes (service=http)

(sid:1) Server, client:2581 bytes (service=http)

(sid:2) Server, client:369 bytes (service=http)

(sid:2) Connection Terminated (by Server)

Where the total number of issues is: 1774

The total number of bytes Received is: 6927

So, after the LoadRunner run, does throughput record the number of bytes sent or the number of bytes received, or the sum of the two? Let's go ahead and do it!

3. Set the script to run 10 times in run time setting

This means that the total number of bytes Sent is 17740 and the total number of bytes Received is 69270

4, run the script in the controller, the scene run mode is set to: Classic schedule

Start Vusers set to: simultaneously

Duration set to: run until completion

5, we anticipate the result of running the scene, where the throughput of the value should be 69270 to prove our argument

6. Operation Scene

7. After the scene runs, click Analyze results to generate the analysis results report.

Analysis Summary period:16/02/2009 15:51:55-16/02/2009 15:52:08

Scenario Name:scenario1

Results in Session:c:\documents and Settings\test\my DOCUMENTS\LR_HTTP\RES\RES.LRR

Duration:13 seconds.

Statistics Summary

Maximum Running vusers:1

Total throughput (bytes): 69,270 (

Equal to the total number of bytes received)

Average throughput (Bytes/second): 4,948

Total hits:40

Average Hits per second:2.857 View HTTP responses Summary

Summary: The total throughput (bytes) in LoadRunner is the total number of bytes returned from the server to the client during the entire testing process, regardless of the number of bytes sent in the request!

Copyright NOTICE: This article for Bo Master original article, without Bo Master permission not reproduced.

Analysis and calculation of throughput (throughput) in LoadRunner