ndn12logic: everything (scoped)
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

1. Load

Load Count
(xact/sec)
Volume
(Mbits/sec)
offered 3.99 0.35
measured 3.88 0.34
load trace
load.trace.scope=sides=client__phases=meas

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.




2. SOCKS load

SOCKS load Count
(xact/sec)
Volume
(Mbits/sec)
offered 0.00 -0.00
measured 0.00 0.00
SOCKS load trace
socks.load.trace.scope=sides=client__phases=meas

The SOCKS 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.




3. SSL load

SSL load Count
(xact/sec)
Volume
(Mbits/sec)
offered 0.00 -0.00
measured 0.00 0.00
SSL load trace
ssl.load.trace.scope=sides=client__phases=meas

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.




4. FTP load

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=meas

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.




5. Mean response time versus response rate

Mean response time versus response rate
rptm-load.scatt.scope=sides=client__phases=meas

6. Client Side Hit Ratios

Client Side Hit Ratios DHR
(%)
BHR
(%)
offered 63.99 64.70
measured 0.00 0.00
Document hit ratio trace
dhr.trace.scope=sides=client__phases=meas
Byte hit ratio trace
bhr.trace.scope=sides=client__phases=meas

The hit ratios table shows offered and measured hit ratios from client side point of view. Polygraph counts every repeated request to a cachable object as an offered hit. Measured (cache) hits are detected using Polygraph-specific headers. All hits are counted for 'basic' transactions only (simple HTTP GET requests with '200 OK' responses).

DHR, Document Hit Ratio, is the ratio of the total number of hits to the number of all basic transactions (hits and misses). BHR, Byte Hit Ratio, is the ratio of the total volume (a sum of response sizes) of hits to the total volume of all basic transactions.

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.




7. Concurrent HTTP transaction level table

Transaction state Number of times Mean concurrency level
entered left
active 7770.00 7568.00 9.17
waiting 0.00 0.00 0.00
concurrent HTTP transaction level trace
xact.level.trace.scope=sides=client__phases=meas

TBD.




8. Concurrent HTTP/TCP connection level table

Connection state Number of times Mean concurrency level
entered left
open 7770.00 7567.00 9.17
established 7594.00 7468.00 7.11
idle 0.00 0.00 0.00
concurrent HTTP/TCP connection level trace
conn.level.trace.scope=sides=client__phases=meas

TBD.




9. Pipelined HTTP connections

probability: 0.00% or 0conn pipelined out of total 7468conn

Figure 'HTTP pipelining depth histogram' not available: no datapoints to plot.

HTTP pipelining trace
conn.pipeline.trace.scope=sides=client__phases=meas

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.




10. Population level table

Number of agents Mean population level
created destroyed
30.00 0.00 30.00
population level trace
populus.level.trace.scope=sides=client__phases=meas

Populus is a set of all live robot or server agents. While alive, an agent may participate in HTTP transactions or remain idle.




11. Reply traffic stream table

Stream Contribution Rates Totals
Count
(%)
Volume
(%)
Count
(xact/sec)
Volume
(Mbits/sec)
Count
(xact,M)
Volume
(Gbyte)
"image" response 66.11 28.06 2.53 0.09 0.00 0.02
"HTML" response 14.10 10.36 0.54 0.03 0.00 0.01
"download" response 0.71 18.02 0.03 0.06 0.00 0.01
"other" response 19.08 43.56 0.73 0.15 0.00 0.03
all response content types 100.00 100.00 3.83 0.34 0.01 0.08
misses 100.00 100.00 3.83 0.34 0.01 0.08
hits and misses 100.00 100.00 3.83 0.34 0.01 0.08
cachable 80.29 81.75 3.08 0.27 0.01 0.07
not cachable 19.71 18.25 0.76 0.06 0.00 0.01
cachable and not 100.00 100.00 3.83 0.34 0.01 0.08
fill 80.29 81.75 3.08 0.27 0.01 0.07
all replies 100.00 100.00 3.83 0.34 0.01 0.08
page n/a[1] n/a[1] 0.54 0.13 0.00 0.03
no auth 100.00 100.00 3.83 0.34 0.01 0.08

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, 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, 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.




12. Request traffic stream table

Stream Contribution Rates Totals
Count
(%)
Volume
(%)
Count
(xact/sec)
Volume
(Mbits/sec)
Count
(xact,M)
Volume
(Gbyte)
"bodiless" request 100.00 100.00 3.83 0.01 0.01 0.00
all request content types 100.00 100.00 3.83 0.01 0.01 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.




13. Reply object kind table

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.75 42.51
"HTML" response n/a[1] n/a[1] n/a[1] 0.28 8.23 59.05
"download" response n/a[1] n/a[1] n/a[1] 228.02 284.34 444.07
"other" response n/a[1] n/a[1] n/a[1] 8.51 25.56 70.02
all response content types n/a[1] n/a[1] n/a[1] 0.24 11.20 444.07
misses 45.00 799.84 9190.00 0.24 11.20 444.07
hits and misses 45.00 799.84 9190.00 0.24 11.20 444.07
cachable 45.00 790.04 9060.00 0.27 11.40 444.07
not cachable 50.00 839.73 9190.00 0.24 10.37 56.62
cachable and not 45.00 799.84 9190.00 0.24 11.20 444.07
fill 45.00 790.04 9060.00 0.27 11.40 444.07
all replies 45.00 799.84 9190.00 0.24 11.20 444.07
page 102.00 1236.85 10828.00 0.28 30.57 103.56
no auth 45.00 799.84 9190.00 0.24 11.20 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, 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, 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.




14. Request object kind table

Object Response time (msec) Size (KBytes)
Min Mean Max Min Mean Max
"bodiless" request n/a[1] n/a[1] n/a[1] 0.36 0.40 0.41
all request content types n/a[1] n/a[1] n/a[1] 0.36 0.40 0.41

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.




15. Validation effectiveness table

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.




16. Errors

The total of 108 errors detected. Out of those errors, 100xact or 1.32% of all transactions were classified as transaction errors.

Error Count Contribution (%)
(s110) Connection timed out 100 92.59
(c33) stale object 7 6.48
(c147) too many errors 1 0.93

The 'Errors' table shows detected errors. For each error type, the number of errors and their contribution towards total error count are shown.




17. Compound reply traffic stream table

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 3.83 0.34 0.01 0.08 3.83

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.




18. Compound request traffic stream table

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 3.83 0.01 0.01 0.00 3.83

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.




19. Compound reply object kind table

Object Response time (msec) Size (KBytes) Parts
Min Mean Max Min Mean Max Min Mean Max
isolated replies 45.00 799.84 9190.00 0.24 11.20 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.




20. Compound request object kind table

Object Response time (msec) Size (KBytes) Parts
Min Mean Max Min Mean Max Min Mean Max
isolated requests 45.00 799.84 9190.00 0.36 0.40 0.41 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.




21. Authentication traffic stream table

Stream Contribution Rates Totals
Count
(%)
Volume
(%)
Count
(xact/sec)
Volume
(Mbits/sec)
Count
(xact,M)
Volume
(Gbyte)
no auth 100.00 100.00 3.83 0.34 0.01 0.08
all replies 100.00 100.00 3.83 0.34 0.01 0.08

No events observed for the following statistics: 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.




22. Authentication object kind table

Object Response time (msec) Size (KBytes)
Min Mean Max Min Mean Max
no auth 45.00 799.84 9190.00 0.24 11.20 444.07
all replies 45.00 799.84 9190.00 0.24 11.20 444.07

No events observed for the following statistics: 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.




23. HTTP reply status traffic stream table

Stream Contribution Rates Totals
Count
(%)
Volume
(%)
Count
(xact/sec)
Volume
(Mbits/sec)
Count
(xact,M)
Volume
(Gbyte)
Other HTTP reply status code 1.32 0.00 0.05 0.00 0.00 0.00
HTTP reply status code 200 98.68 100.00 3.83 0.34 0.01 0.08
All HTTP reply status codes 100.00 100.00 3.88 0.34 0.01 0.08

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.




24. HTTP reply status codes table

Object Response time (msec) Size (KBytes)
Min Mean Max Min Mean Max
HTTP reply status code 200 45.00 799.84 9190.00 0.24 11.20 444.07
Other HTTP reply status code 21000.00 21000.02 21001.00 0.00 0.00 0.00
All HTTP reply status codes 45.00 1066.75 21001.00 0.00 11.05 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.




25. HTTP Cookies 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
fresh cookies evicted: 0.00cookie
stale cookies evicted: 0.00cookie
cookies updated: 0.00cookie

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.




26. Object '"image" response'

contribution: 66.11% by count and 28.06% by volume
rates: 2.53/sec or 0.09Mbits/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, 4.75KBytes 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.


27. Object '"HTML" response'

contribution: 14.10% by count and 10.36% by volume
rates: 0.54/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: 0.28KBytes min, 8.23KBytes 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.


28. Object '"download" response'

contribution: 0.71% by count and 18.02% by volume
rates: 0.03/sec or 0.06Mbits/sec
totals: 0.00M and 0.01GByte
response time: n/a[1] min, n/a[1] mean, and n/a[1] max
response size: 228.02KBytes min, 284.34KBytes 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.


29. Object '"other" response'

contribution: 19.08% by count and 43.56% by volume
rates: 0.73/sec or 0.15Mbits/sec
totals: 0.00M and 0.03GByte
response time: n/a[1] min, n/a[1] mean, and n/a[1] max
response size: 8.51KBytes min, 25.56KBytes 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.


30. Object 'all response content types'

contribution: 100.00% by count and 100.00% by volume
rates: 3.83/sec or 0.34Mbits/sec
totals: 0.01M and 0.08GByte
response time: n/a[1] min, n/a[1] mean, and n/a[1] max
response size: 0.24KBytes min, 11.20KBytes 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.




31. Object 'misses'

contribution: 100.00% by count and 100.00% by volume
rates: 3.83/sec or 0.34Mbits/sec
totals: 0.01M and 0.08GByte
response time: 45.00msec min, 799.84msec mean, and 9190.00msec max
response size: 0.24KBytes min, 11.20KBytes mean, and 444.07KBytes max
response time distribution
object.misses.rptm.fig.scope=sides=client__phases=meas
object size distribution
object.misses.size.fig.scope=sides=client__phases=meas
load trace
object.misses.load.trace.scope=sides=client__phases=meas
response time trace
object.misses.rptm.trace.scope=sides=client__phases=meas

No description is available for this object class.

This object class belongs to the 'hits and misses' class.




32. Object 'hits and misses'

contribution: 100.00% by count and 100.00% by volume
rates: 3.83/sec or 0.34Mbits/sec
totals: 0.01M and 0.08GByte
response time: 45.00msec min, 799.84msec mean, and 9190.00msec max
response size: 0.24KBytes min, 11.20KBytes mean, and 444.07KBytes max
response time distribution
object.hits_and_misses.rptm.fig.scope=sides=client__phases=meas
object size distribution
object.hits_and_misses.size.fig.scope=sides=client__phases=meas
load trace
object.hits_and_misses.load.trace.scope=sides=client__phases=meas
response time trace
object.hits_and_misses.rptm.trace.scope=sides=client__phases=meas

No description is available for this object class.

This object class belongs to the 'all replies' class.




33. Object 'cachable'

contribution: 80.29% by count and 81.75% by volume
rates: 3.08/sec or 0.27Mbits/sec
totals: 0.01M and 0.07GByte
response time: 45.00msec min, 790.04msec mean, and 9060.00msec max
response size: 0.27KBytes min, 11.40KBytes mean, and 444.07KBytes max

No response time and size histograms were collected or stored for this object class.

load trace
object.cachable.load.trace.scope=sides=client__phases=meas
response time trace
object.cachable.rptm.trace.scope=sides=client__phases=meas

No description is available for this object class.

This object class belongs to the 'cachable and not' class.




34. Object 'not cachable'

contribution: 19.71% by count and 18.25% by volume
rates: 0.76/sec or 0.06Mbits/sec
totals: 0.00M and 0.01GByte
response time: 50.00msec min, 839.73msec mean, and 9190.00msec max
response size: 0.24KBytes min, 10.37KBytes mean, and 56.62KBytes max

No response time and size histograms were collected or stored for this object class.

load trace
object.uncachable.load.trace.scope=sides=client__phases=meas
response time trace
object.uncachable.rptm.trace.scope=sides=client__phases=meas

No description is available for this object class.

This object class belongs to the 'cachable and not' class.




35. Object 'cachable and not'

contribution: 100.00% by count and 100.00% by volume
rates: 3.83/sec or 0.34Mbits/sec
totals: 0.01M and 0.08GByte
response time: 45.00msec min, 799.84msec mean, and 9190.00msec max
response size: 0.24KBytes min, 11.20KBytes mean, and 444.07KBytes max

No response time and size histograms were collected or stored for this object class.

load trace
object.all_cachable.load.trace.scope=sides=client__phases=meas
response time trace
object.all_cachable.rptm.trace.scope=sides=client__phases=meas

No description is available for this object class.

This object class belongs to the 'all replies' class.




36. Object 'fill'

contribution: 80.29% by count and 81.75% by volume
rates: 3.08/sec or 0.27Mbits/sec
totals: 0.01M and 0.07GByte
response time: 45.00msec min, 790.04msec mean, and 9060.00msec max
response size: 0.27KBytes min, 11.40KBytes mean, and 444.07KBytes max

No response time and size histograms were collected or stored for this object class.

load trace
object.fill.load.trace.scope=sides=client__phases=meas
response time trace
object.fill.rptm.trace.scope=sides=client__phases=meas

No description is available for this object class.

This object class belongs to the 'all replies' class.




37. Object 'all replies'

contribution: 100.00% by count and 100.00% by volume
rates: 3.83/sec or 0.34Mbits/sec
totals: 0.01M and 0.08GByte
response time: 45.00msec min, 799.84msec mean, and 9190.00msec max
response size: 0.24KBytes min, 11.20KBytes mean, and 444.07KBytes max
response time distribution
object.rep.rptm.fig.scope=sides=client__phases=meas
object size distribution
object.rep.size.fig.scope=sides=client__phases=meas
load trace
object.rep.load.trace.scope=sides=client__phases=meas
response time trace
object.rep.rptm.trace.scope=sides=client__phases=meas

No description is available for this object class.




38. Object 'page'

rates: 0.54/sec or 0.13Mbits/sec
totals: 0.00M and 0.03GByte
response time: 102.00msec min, 1236.85msec mean, and 10828.00msec max
response size: 0.28KBytes min, 30.57KBytes mean, and 103.56KBytes max
response time distribution
object.page.rptm.fig.scope=sides=client__phases=meas
object size distribution
object.page.size.fig.scope=sides=client__phases=meas
load trace
object.page.load.trace.scope=sides=client__phases=meas
response time trace
object.page.rptm.trace.scope=sides=client__phases=meas

No description is available for this object class.




39. Object 'no auth'

contribution: 100.00% by count and 100.00% by volume
rates: 3.83/sec or 0.34Mbits/sec
totals: 0.01M and 0.08GByte
response time: 45.00msec min, 799.84msec mean, and 9190.00msec max
response size: 0.24KBytes min, 11.20KBytes mean, and 444.07KBytes max

No response time and size histograms were collected or stored for this object class.

load trace
object.auth.none.load.trace.scope=sides=client__phases=meas
response time trace
object.auth.none.rptm.trace.scope=sides=client__phases=meas

No description is available for this object class.

This object class belongs to the 'all replies' class.




40. Object '"bodiless" request'

contribution: 100.00% by count and 100.00% by volume
rates: 3.83/sec or 0.01Mbits/sec
totals: 0.01M and 0.00GByte
response time: n/a[1] min, n/a[1] mean, and n/a[1] max
response size: 0.36KBytes min, 0.40KBytes mean, and 0.41KBytes 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.


41. Object 'all request content types'

contribution: 100.00% by count and 100.00% by volume
rates: 3.83/sec or 0.01Mbits/sec
totals: 0.01M and 0.00GByte
response time: n/a[1] min, n/a[1] mean, and n/a[1] max
response size: 0.36KBytes min, 0.40KBytes mean, and 0.41KBytes 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.




42. Object 'isolated replies'

contribution: 100.00% by count and 100.00% by volume
rates: 3.83/sec or 0.34Mbits/sec
totals: 0.01M and 0.08GByte
response time: 45.00msec min, 799.84msec mean, and 9190.00msec max
response size: 0.24KBytes min, 11.20KBytes 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.




43. Object 'isolated requests'

contribution: 100.00% by count and 100.00% by volume
rates: 3.83/sec or 0.01Mbits/sec
totals: 0.01M and 0.00GByte
response time: 45.00msec min, 799.84msec mean, and 9190.00msec max
response size: 0.36KBytes min, 0.40KBytes mean, and 0.41KBytes 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 request content types' class.




44. Object 'HTTP reply status code 200'

contribution: 98.68% by count and 100.00% by volume
rates: 3.83/sec or 0.34Mbits/sec
totals: 0.01M and 0.08GByte
response time: 45.00msec min, 799.84msec mean, and 9190.00msec max
response size: 0.24KBytes min, 11.20KBytes 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 HTTP reply status codes' class.




45. Object 'Other HTTP reply status code'

contribution: 1.32% by count and 0.00% by volume
rates: 0.05/sec or 0.00Mbits/sec
totals: 0.00M and 0.00GByte
response time: 21000.00msec min, 21000.02msec mean, and 21001.00msec max
response size: 0.00KBytes min, 0.00KBytes mean, and 0.00KBytes 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 HTTP reply status codes' class.




46. Object 'All HTTP reply status codes'

rates: 3.88/sec or 0.34Mbits/sec
totals: 0.01M and 0.08GByte
response time: 45.00msec min, 1066.75msec mean, and 21001.00msec max
response size: 0.00KBytes min, 11.05KBytes 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.




47. Unseen objects

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, 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, 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, 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.