This information is based on the client-side measurements.
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.
|all content types||85.91||88.21||1096.28||60.98||15.79||107.21|
|hits and misses||85.91||88.21||1096.28||60.98||15.79||107.21|
|cachable and not||85.91||88.21||1096.28||60.98||15.79||107.21|
|reply to redirect||0.00||0.00||0.00||0.00||0.00||0.00|
The 'Stream' table provides count and volume statistics for many classes of transactions. 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 'Object' table contains corresponding response time and size statistics for streams.