Analysis and Calculation of throughput (throughput) in LoadRunner

Analysis and Calculation of throughput (throughput) in LoadRunner

Core tips:Throughput is translated as throughput. According to the general understanding, network throughput indicates the sum of the data volume of the network adapter in a unit of time.

Throughput is translated as throughput. According to the general understanding, network throughput indicates the sum of the data volumes sent by the NIC per unit time, which includes the data volumes received by the NIC, however, this understanding is incorrect in the throughput record of LoadRunner!
First, the correct results are presented, and then proved by specific experiments:

The throughput of the LoadRunner record is the sum of the number of all bytes received by the server. It is irrelevant to the number of locally sent bytes!

　　We use Baidu.com for an experiment. The process is simple:

1. Use vugen to record the Baidu homepage. Open the homepage only.

2. Record the sending status of client and server data in the recording log, and count the total number of sent bytes and the total number of received bytes.

The 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)

The total number of outgoing requests is: 1774

Total number of received Bytes: 6927

After LoadRunner runs, does throughput record the number of sent bytes, the number of received bytes, or the sum of the two? Let's continue!

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

That is to say, the total number of sent bytes is 17740, and the total number of received bytes is 69270.

4. Run the script in controller. Set the scenario running mode to classic schedule.

Set start vusers to simultaneously.

Set duration to run until completion.

5. We predict the result of running this scenario. The throughput value should be 69270, which proves our statement.

6. Running scenario

7. After the scenario is run, click analysis results to generate the analysis result report.

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

Scenario name: scenario1

Results In session: C: \ Documents ents and Settings \ test \ My Documents ents \ lr_http \ res. LRR

Duration: 13 seconds.

Statistics Summary

Maximum running vusers: 1

Total Throughput (bytes): 69,270 (

Same as 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) count in LoadRunner is the number of all bytes returned to the client from the server throughout the test, regardless of the number of bytes sent to the client!