Base test with 2000 concurrent connections: traffic rates, counts, and volumes

This information is based on the client-side measurements.

Load Count
(xact/sec)
Volume
(Mbits/sec)
offered 234.31 1.34
measured 234.16 1.33
load trace
load.trace.scope=sides=client__phases=ph16000

The load table shows offered and measured load from client side point of view. Offered load statistics are based on the request stream. Measured load statistics are based on reply messages. The 'count' column depicts the number of requests or responses.

The 'volume' column is a little bit more tricky to interpret. Offered volume is reply bandwidth that would have been required to support offered load. This volume is computed as request rate multiplied by measured mean response size. Measured volume is the actual or measured reply bandwidth.



SSL load Count
(xact/sec)
Volume
(Mbits/sec)
offered 234.31 1.34
measured 234.16 1.33
SSL load trace
ssl.load.trace.scope=sides=client__phases=ph16000

The SSL load table shows offered and measured load from client side point of view. Offered load statistics are based on the request stream. Measured load statistics are based on reply messages. The 'count' column depicts the number of requests or responses.

The 'volume' column is a little bit more tricky to interpret. Offered volume is reply bandwidth that would have been required to support offered load. This volume is computed as request rate multiplied by measured mean response size. Measured volume is the actual or measured reply bandwidth.



FTP load Count
(xact/sec)
Volume
(Mbits/sec)
offered 0.00 -0.00
measured 0.00 0.00
FTP load trace
ftp.load.trace.scope=sides=client__phases=ph16000

The FTP load table shows offered and measured load from client side point of view. Offered load statistics are based on the request stream. Measured load statistics are based on reply messages. The 'count' column depicts the number of requests or responses.

The 'volume' column is a little bit more tricky to interpret. Offered volume is reply bandwidth that would have been required to support offered load. This volume is computed as request rate multiplied by measured mean response size. Measured volume is the actual or measured reply bandwidth.



Stream Contribution Rates Totals
Count
(%)
Volume
(%)
Count
(xact/sec)
Volume
(Mbits/sec)
Count
(xact,M)
Volume
(Gbyte)
"bodiless" response 53.52 7.66 124.71 0.10 0.11 0.01
"const_1KB_objects" response 46.48 92.34 108.32 1.23 0.09 0.13
all response content types 100.00 100.00 233.03 1.33 0.20 0.14
misses 36.20 71.90 84.35 0.96 0.07 0.10
hits and misses 36.20 71.90 84.35 0.96 0.07 0.10
ims/200 3.80 7.55 8.87 0.10 0.01 0.01
ims/304 3.66 1.45 8.52 0.02 0.01 0.00
all ims 7.46 9.00 17.39 0.12 0.01 0.01
cachable 36.20 71.90 84.35 0.96 0.07 0.10
cachable and not 36.20 71.90 84.35 0.96 0.07 0.10
fill 36.20 71.90 84.35 0.96 0.07 0.10
reload 2.50 4.96 5.82 0.07 0.00 0.01
HEAD 0.04 0.03 0.10 0.00 0.00 0.00
POST 3.99 7.93 9.30 0.11 0.01 0.01
CONNECT 49.81 6.18 116.08 0.08 0.10 0.01
all non-gets 53.85 14.14 125.48 0.19 0.11 0.02
all replies 100.00 100.00 233.03 1.33 0.20 0.14
SSL misses 100.00 100.00 233.03 1.33 0.20 0.14
SSL hits and misses 100.00 100.00 233.03 1.33 0.20 0.14
tunneled 100.00 100.00 233.03 1.33 0.20 0.14

No events observed for the following statistics: "foreign" response, "unknown" response, hits, not cachable, FTP active, FTP passive, FTP all modes, range, abort, redirected request, reply to redirect, PUT, page, useful proxy validations, useless proxy validations, all proxy validations, SOCKS hits, SOCKS misses, SOCKS hits and misses, SSL hits, FTP hits, FTP misses, FTP hits and misses, no auth, all auth, custom.


The 'Reply stream' table provides count and volume statistics for many classes of transactions and for so-called pages. The 'Contribution' columns show count- and volume-based portions of all transactions. The 'Rates' columns show throughput and bandwidth measurements. The 'Totals' columns contain the total number of transactions and the total volume (a sum of individual response sizes) for each stream.

Note that some streams are a combination of other streams. For example, the 'all ims' stream contains transactions with If-Modified-Since requests that resulted in either '200 OK' (the 'ims/304' stream) or '304 Not Modified' (the 'ims/304' stream) responses.

Many combination streams, such as 'all content types' or 'hits and misses' stream, contribute less than 100% because properties like content type or hit status are distinguished for 'basic' transactions only. A basic transactions is a simple HTTP GET request resulted in a '200 OK' response. Various special transactions such as IMS or aborts do not belong to the 'basic' category.

The 'Reply object' table contains corresponding response time and size statistics for streams.

A similar table covering request messages is available elsewhere.