client side | baseline | all phases | meas |
---|---|---|---|
server side | baseline | all phases | meas |
all sides | baseline | all phases | meas |
highlighted cell(s) above show current scope |
---|
links point to other scopes |
load trace
The load table shows offered and measured load from server 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.
SOCKS load trace
The SOCKS load table shows offered and measured load from server 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 trace
The SSL load table shows offered and measured load from server 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 trace
The FTP load table shows offered and measured load from server 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.
Client Side Hit Ratios DHR
(%)BHR
(%)offered 0.00 0.00 measured 0.00 0.00
Document hit ratio trace
Byte hit ratio trace
The server-side hit ratios should always be zero. If a request reaches a server, it is, by definition, a miss.
A better way to measure hit ratio is to compare client- and server-side traffic. A hit ratio table based on such a comparison is available elsewhere.
Figure 'HTTP pipelining depth histogram' not available: no datapoints to plot.
HTTP pipelining trace
Connection pipelining stats are based on measurements collected for pipelined HTTP connections. To calculate pipelining probability, a connection is counted as pipelined if it had pipelined (concurrent) requests pending at any given moment of its lifetime.
The pipeline depth varies as new requests are added to the connection and old requests are satisfied by responses. The depth reported her is based on the maximum pipelining depth achieved during a pipelined connection lifetime. That is, the depth stats are collected everytime a pipelined connection is closed, not when a new request is added to or removed from the pipe.
Stream Contribution Rates Totals Count
(%)Volume
(%)Count
(xact/sec)Volume
(Mbits/sec)Count
(xact,M)Volume
(Gbyte)"image" response 64.14 26.93 0.53 0.02 0.00 0.00 "HTML" response 14.34 11.57 0.12 0.01 0.00 0.00 "download" response 0.59 15.35 0.00 0.01 0.00 0.00 "other" response 20.92 46.15 0.17 0.03 0.00 0.01 all response content types 100.00 100.00 0.82 0.07 0.00 0.02 misses 100.00 100.00 0.82 0.07 0.00 0.02 hits and misses 100.00 100.00 0.82 0.07 0.00 0.02 cachable 80.07 81.28 0.66 0.06 0.00 0.01 not cachable 19.93 18.72 0.16 0.01 0.00 0.00 cachable and not 100.00 100.00 0.82 0.07 0.00 0.02 fill 80.07 81.28 0.66 0.06 0.00 0.01 all replies 100.00 100.00 0.82 0.07 0.00 0.02 No events observed for the following statistics: "foreign" response, "bodiless" response, "unknown" response, hits, ims/200, ims/304, all ims, FTP active, FTP passive, FTP all modes, reload, range, abort, redirected request, reply to redirect, HEAD, POST, PUT, CONNECT, all non-gets, page, useful proxy validations, useless proxy validations, all proxy validations, SOCKS hits, SOCKS misses, SOCKS hits and misses, SSL hits, SSL misses, SSL hits and misses, FTP hits, FTP misses, FTP hits and misses, no auth, all auth, tunneled, 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.
Stream Contribution Rates Totals Count
(%)Volume
(%)Count
(xact/sec)Volume
(Mbits/sec)Count
(xact,M)Volume
(Gbyte)"bodiless" request 100.00 100.00 0.82 0.00 0.00 0.00 all request content types 100.00 100.00 0.82 0.00 0.00 0.00 No events observed for the following statistics: "HTML" request, "download" request, "foreign" request, "image" request, "other" request, "unknown" request.
The 'Request stream' table provides count and volume statistics for requests. 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 request sizes) for each stream.
Note that some streams are a combination of other streams. For example, the 'all request content types' stream contains requests with different content types.
Note that only request messages containing bodies contribute to these stats at the moment.
The 'Request object' table contains corresponding response time and size statistics for streams.
A similar table covering reply messages is available elsewhere.
Object Response time (msec) Size (KBytes) Min Mean Max Min Mean Max "image" response n/a[1] n/a[1] n/a[1] 0.24 4.85 42.51 "HTML" response n/a[1] n/a[1] n/a[1] 0.28 9.31 59.05 "download" response n/a[1] n/a[1] n/a[1] 228.02 299.25 444.07 "other" response n/a[1] n/a[1] n/a[1] 8.51 25.46 70.02 all response content types n/a[1] n/a[1] n/a[1] 0.24 11.54 444.07 misses 0.00 0.08 19.00 0.24 11.54 444.07 hits and misses 0.00 0.08 19.00 0.24 11.54 444.07 cachable 0.00 0.10 19.00 0.27 11.72 444.07 not cachable 0.00 0.00 0.00 0.24 10.84 56.62 cachable and not 0.00 0.08 19.00 0.24 11.54 444.07 fill 0.00 0.10 19.00 0.27 11.72 444.07 all replies 0.00 0.08 19.00 0.24 11.54 444.07 No events observed for the following statistics: "foreign" response, "bodiless" response, "unknown" response, hits, ims/200, ims/304, all ims, FTP active, FTP passive, FTP all modes, reload, range, abort, redirected request, reply to redirect, HEAD, POST, PUT, CONNECT, all non-gets, page, useful proxy validations, useless proxy validations, all proxy validations, SOCKS hits, SOCKS misses, SOCKS hits and misses, SSL hits, SSL misses, SSL hits and misses, FTP hits, FTP misses, FTP hits and misses, no auth, all auth, tunneled, custom.
The 'Reply object' table provides response time and response size statistics for many classes of transactions and for so-called pages.
Note that some classes are a combination of other classes. For example, the 'all ims' class contains transactions with If-Modified-Since requests that resulted in either '200 OK' (the 'ims/304' class) or '304 Not Modified' (the 'ims/304' class) responses.
Some statistics may not be available because either no objects of the corresponding class were seen during the test or no facilities to collect the stats exist for the class. The former can be verified using a 'Reply stream' table.
A similar table covering request messages is available elsewhere.
Object Response time (msec) Size (KBytes) Min Mean Max Min Mean Max "bodiless" request n/a[1] n/a[1] n/a[1] 0.12 0.13 0.13 all request content types n/a[1] n/a[1] n/a[1] 0.12 0.13 0.13 No events observed for the following statistics: "foreign" request, "unknown" request, "image" request, "HTML" request, "download" request, "other" request.
The 'Request object' table provides time and size statistics for requests.
Note that some classes are a combination of other classes. For example, the 'all request content types' class contains requests with different content type.
Note that only request messages containing bodies contribute to these stats at the moment.
Some statistics may not be available because either no objects of the corresponding class were seen during the test or no facilities to collect the stats exist for the class. The former can be verified using a 'Request stream' table.
A similar table covering reply messages is available elsewhere.
Validation method Useful count
(%)Useful volume
(%)Proxy validation -1.00 -1.00
The 'Validation effectiveness' table shows useful request ratios for various validation methods. Polygraph counts every validation request that results in bodyless response as useless. Validation requests that result in response with body are useful.
The total of 3040 errors detected. Out of those errors, 0xact or 0.00% of all transactions were classified as transaction errors.
Error Count Contribution (%) (c8) foreign host name 1520 50.00 (c13) missing target info in the request 1520 50.00
The 'Errors' table shows detected errors. For each error type, the number of errors and their contribution towards total error count are shown.
Stream Contribution Rates Totals Parts Count
(%)Volume
(%)Count
(xact/sec)Volume
(Mbits/sec)Count
(xact,M)Volume
(Gbyte)Count
(xact/sec)isolated replies 100.00 100.00 0.82 0.07 0.00 0.02 0.82 No events observed for the following statistics: Basic auth replies, NTLM auth replies, Negotiate auth replies, all compound replies.
A compound transaction consists of related transactions, working on a single goal such as authenticating a transfer. While individual transactions consist of a single request/response pair, compound transactions usually have several such pairs. Isolated transactions are individual transactions that do not belong to any compound transaction.
Stats in the 'Compound reply stream' table provides count and volume statistics for responses. The 'Contribution' columns show count- and volume-based portions of all compound transactions (isolated transaction not included). 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 request sizes) for each stream. The 'Parts' column shows individual transactions rate in a compound transaction.
The 'Compound reply object' table contains corresponding response time and size statistics for streams.
A similar table covering request messages is available elsewhere.
Stream Contribution Rates Totals Parts Count
(%)Volume
(%)Count
(xact/sec)Volume
(Mbits/sec)Count
(xact,M)Volume
(Gbyte)Count
(xact/sec)isolated requests 100.00 100.00 0.82 0.00 0.00 0.00 0.82 No events observed for the following statistics: Basic auth requests, NTLM auth requests, Negotiate auth requests, all compound requests.
A compound transaction consists of related transactions, working on a single goal such as authenticating a transfer. While individual transactions consist of a single request/response pair, compound transactions usually have several such pairs. Isolated transactions are individual transactions that do not belong to any compound transaction.
Stats in the 'Compound request stream' table provides count and volume statistics for requests. The 'Contribution' columns show count- and volume-based portions of all compound transactions (isolated transaction not included). 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 request sizes) for each stream. The 'Parts' column shows individual transactions rate in a compound transaction.
The 'Compound request object' table contains corresponding request time and size statistics for streams.
A similar table covering reply messages is available elsewhere.
Object Response time (msec) Size (KBytes) Parts Min Mean Max Min Mean Max Min Mean Max isolated replies 0.00 0.08 19.00 0.24 11.54 444.07 1.00 1.00 1.00 No events observed for the following statistics: Basic auth replies, NTLM auth replies, Negotiate auth replies, all compound replies.
A compound transaction consists of related transactions, working on a single goal such as authenticating a transfer. While individual transactions consist of a single request/response pair, compound transactions usually have several such pairs. Isolated transactions are individual transactions that do not belong to any compound transaction.
Stats in the 'Compound reply object' table provides time and size statistics for responses. Compound transaction response time is time from the start of the first transaction until the end of the last one. Request (response) size is the total size of all individual requests (responses) in a compound transaction. The 'Parts' column shows the number of individual transactions in a compound transaction.
The 'Compound reply stream' table contains corresponding stream statistics.
A similar table covering request messages is available elsewhere.
Object Response time (msec) Size (KBytes) Parts Min Mean Max Min Mean Max Min Mean Max isolated requests 0.00 0.08 19.00 0.12 0.13 0.13 1.00 1.00 1.00 No events observed for the following statistics: Basic auth requests, NTLM auth requests, Negotiate auth requests, all compound requests.
A compound transaction consists of related transactions, working on a single goal such as authenticating a transfer. While individual transactions consist of a single request/response pair, compound transactions usually have several such pairs. Isolated transactions are individual transactions that do not belong to any compound transaction.
Stats in the 'Compound request object' table provides time and size statistics for requests. Compound transaction response time is time from the start of the first transaction until the end of the last one. Request (response) size is the total size of all individual requests (responses) in a compound transaction. The 'Parts' column shows the number of individual transactions in a compound transaction.
The 'Compound request stream' table contains corresponding stream statistics.
A similar table covering response messages is available elsewhere.
Stream Contribution Rates Totals Count
(%)Volume
(%)Count
(xact/sec)Volume
(Mbits/sec)Count
(xact,M)Volume
(Gbyte)all replies 100.00 100.00 0.82 0.07 0.00 0.02 No events observed for the following statistics: no auth, Basic auth-ing, NTLM auth-ing, Negotiate auth-ing, all auth-ing, Basic auth-ed, NTLM auth-ed, Negotiate auth-ed, FTP auth, all auth-ed, all auth, tunneled.
The 'Authentication stream' table provides count and volume statistics for authentication-related 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 auth-ing' stream contains auth-ing transactions with any authentication scheme.
The 'Authentication object' table contains corresponding response time and size statistics for streams.
Object Response time (msec) Size (KBytes) Min Mean Max Min Mean Max all replies 0.00 0.08 19.00 0.24 11.54 444.07 No events observed for the following statistics: no auth, Basic auth-ing, NTLM auth-ing, Negotiate auth-ing, all auth-ing, Basic auth-ed, NTLM auth-ed, Negotiate auth-ed, FTP auth, all auth-ed, all auth, tunneled.
The 'Authentication object' table provides response time and response size statistics authentication-related tansactions.
Note that some streams are a combination of other streams. For example, the 'all auth-ing' stream contains auth-ing transactions with any authentication scheme.
Some statistics may not be available because either no objects of the corresponding class were seen during the test or no facilities to collect the stats exist for the class. The former can be verified using a 'Authentication stream' table.
Stream Contribution Rates Totals Count
(%)Volume
(%)Count
(xact/sec)Volume
(Mbits/sec)Count
(xact,M)Volume
(Gbyte)HTTP reply status code 200 100.00 100.00 0.82 0.07 0.00 0.02 All HTTP reply status codes 100.00 100.00 0.82 0.07 0.00 0.02
The 'HTTP reply status stream' table provides count and volume statistics for HTTP responses with different status codes. The 'Contribution' columns show count- and volume-based portions of all replies. 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. 'Other HTTP reply status code' stream contains transactions with errors, e.g. parsing or connection failure, where response status code is unknown.
The 'All HTTP reply status codes' stream contains statistics for responses with all status codes.
The 'HTTP reply status codes' table contains corresponding response time and size statistics.
Object Response time (msec) Size (KBytes) Min Mean Max Min Mean Max HTTP reply status code 200 0.00 0.08 19.00 0.24 11.54 444.07 All HTTP reply status codes 0.00 0.08 19.00 0.24 11.54 444.07
The 'HTTP reply status codes' table provides response time and response size statistics for HTTP transactions with different status codes. 'Other HTTP reply status code' stream contains transactions with errors, e.g. parsing or connection failure, where response status code is unknown.
The 'All HTTP reply status codes' stream contains statistics for responses with all status codes.
See also: 'HTTP reply status stream' table.
Stream #Messages with cookies #Cookies in messages Total #cookies Absolute Relative Min Mean Max Sent 0.00 0.00 -1.00 -1.00 -1.00 0.00 Received 0.00 0.00 -1.00 -1.00 -1.00 0.00
The 'HTTP Cookies' table provides statistics for HTTP cookies sent and received. The 'Messages with cookies' column shows the absolute and relative number of HTTP messages containing cookies. The 'Cookies per message' column shows mininum, maximum, and mean number of cookies in HTTP messages containing cookies. The 'Total #cookies' column shows the total number of cookies sent and received.
contribution: 64.14% by count and 26.93% by volume rates: 0.53/sec or 0.02Mbits/sec totals: 0.00M and 0.00GByte response time: n/a[1] min, n/a[1] mean, and n/a[1] max response size: 0.24KBytes min, 4.85KBytes mean, and 42.51KBytes max No response time and size histograms were collected or stored for this object class.
No response time and size traces are collected for this object class.
This object class represents one of the content types specified in the PGL workload file and labeled there as "image" response content type.
contribution: 14.34% by count and 11.57% by volume rates: 0.12/sec or 0.01Mbits/sec totals: 0.00M and 0.00GByte response time: n/a[1] min, n/a[1] mean, and n/a[1] max response size: 0.28KBytes min, 9.31KBytes mean, and 59.05KBytes max No response time and size histograms were collected or stored for this object class.
No response time and size traces are collected for this object class.
This object class represents one of the content types specified in the PGL workload file and labeled there as "HTML" response content type.
contribution: 0.59% by count and 15.35% by volume rates: 0.00/sec or 0.01Mbits/sec totals: 0.00M and 0.00GByte response time: n/a[1] min, n/a[1] mean, and n/a[1] max response size: 228.02KBytes min, 299.25KBytes mean, and 444.07KBytes max No response time and size histograms were collected or stored for this object class.
No response time and size traces are collected for this object class.
This object class represents one of the content types specified in the PGL workload file and labeled there as "download" response content type.
contribution: 20.92% by count and 46.15% by volume rates: 0.17/sec or 0.03Mbits/sec totals: 0.00M and 0.01GByte response time: n/a[1] min, n/a[1] mean, and n/a[1] max response size: 8.51KBytes min, 25.46KBytes mean, and 70.02KBytes max No response time and size histograms were collected or stored for this object class.
No response time and size traces are collected for this object class.
This object class represents one of the content types specified in the PGL workload file and labeled there as "other" response content type.
contribution: 100.00% by count and 100.00% by volume rates: 0.82/sec or 0.07Mbits/sec totals: 0.00M and 0.02GByte response time: n/a[1] min, n/a[1] mean, and n/a[1] max response size: 0.24KBytes min, 11.54KBytes mean, and 444.07KBytes max No response time and size histograms were collected or stored for this object class.
No response time and size traces are collected for this object class.
No description is available for this object class.
This object class belongs to the 'all replies' class.
response time distribution
object size distribution
load trace
response time trace
No description is available for this object class.
This object class belongs to the 'hits and misses' class.
response time distribution
object size distribution
load trace
response time trace
No description is available for this object class.
This object class belongs to the 'all replies' class.
No response time and size histograms were collected or stored for this object class.
load trace
response time trace
No description is available for this object class.
This object class belongs to the 'cachable and not' class.
No response time and size histograms were collected or stored for this object class.
load trace
response time trace
No description is available for this object class.
This object class belongs to the 'cachable and not' class.
No response time and size histograms were collected or stored for this object class.
load trace
response time trace
No description is available for this object class.
This object class belongs to the 'all replies' class.
No response time and size histograms were collected or stored for this object class.
load trace
response time trace
No description is available for this object class.
This object class belongs to the 'all replies' class.
response time distribution
object size distribution
load trace
response time trace
No description is available for this object class.
contribution: 100.00% by count and 100.00% by volume rates: 0.82/sec or 0.00Mbits/sec totals: 0.00M and 0.00GByte response time: n/a[1] min, n/a[1] mean, and n/a[1] max response size: 0.12KBytes min, 0.13KBytes mean, and 0.13KBytes max No response time and size histograms were collected or stored for this object class.
No response time and size traces are collected for this object class.
This object class represents one of the content types specified in the PGL workload file and labeled there as "bodiless" request content type.
contribution: 100.00% by count and 100.00% by volume rates: 0.82/sec or 0.00Mbits/sec totals: 0.00M and 0.00GByte response time: n/a[1] min, n/a[1] mean, and n/a[1] max response size: 0.12KBytes min, 0.13KBytes mean, and 0.13KBytes max No response time and size histograms were collected or stored for this object class.
No response time and size traces are collected for this object class.
No description is available for this object class.
No response time and size histograms were collected or stored for this object class.
No response time and size traces are collected for this object class.
No description is available for this object class.
This object class belongs to the 'all replies' class.
No response time and size histograms were collected or stored for this object class.
No response time and size traces are collected for this object class.
No description is available for this object class.
This object class belongs to the 'all request content types' class.
No response time and size histograms were collected or stored for this object class.
No response time and size traces are collected for this object class.
No description is available for this object class.
This object class belongs to the 'All HTTP reply status codes' class.
rates: 0.82/sec or 0.07Mbits/sec totals: 0.00M and 0.02GByte response time: 0.00msec min, 0.08msec mean, and 19.00msec max response size: 0.24KBytes min, 11.54KBytes mean, and 444.07KBytes max No response time and size histograms were collected or stored for this object class.
No response time and size traces are collected for this object class.
No description is available for this object class.
No instances of these objects were observed or recorded in the given scope: "foreign" response, "bodiless" response, "unknown" response, hits, ims/200, ims/304, all ims, FTP active, FTP passive, FTP all modes, reload, range, abort, redirected request, reply to redirect, HEAD, POST, PUT, CONNECT, all non-gets, page, useful proxy validations, useless proxy validations, all proxy validations, SOCKS hits, SOCKS misses, SOCKS hits and misses, SSL hits, SSL misses, SSL hits and misses, FTP hits, FTP misses, FTP hits and misses, no auth, all auth, tunneled, custom, "foreign" request, "unknown" request, "image" request, "HTML" request, "download" request, "other" request, Basic auth replies, NTLM auth replies, Negotiate auth replies, all compound replies, Basic auth requests, NTLM auth requests, Negotiate auth requests, all compound requests, no auth, Basic auth-ing, NTLM auth-ing, Negotiate auth-ing, all auth-ing, Basic auth-ed, NTLM auth-ed, Negotiate auth-ed, FTP auth, all auth-ed, all auth, tunneled.
An object unseen in one scope may be present in another scope.