This information is based on the client-side measurements.
|Response times trace|
|Object||Response time (msec)||Size (KBytes)|
|all response content types||n/a||n/a||n/a||0.09||0.74||1.47|
|hits and misses||12.00||203.13||3971.00||1.42||1.45||1.47|
|cachable and not||12.00||203.13||3971.00||1.42||1.45||1.47|
|SSL hits and misses||2.00||217.79||3971.00||0.09||0.74||1.47|
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 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.
|Byte Latency||Written (msec)||Read (msec)|
|Last request byte||0.00||65.89||3420.00||0.00||52.68||112.00|
|First response byte||0.00||29.33||113.00||12.00||202.80||3971.00|
The 'first response byte' latency is the time it took Polygraph to read (or write) the first response byte. The timer starts when the transaction starts. The timer stops when the server writes the first response byte to the TCP socket or the client reads the first response byte from the socket.
Similarly, the 'last request byte' latency is the time it took Polygraph to read (or write) the last request byte. The timer starts when the transaction starts. The timer stop when the client writes the last request byte or the server reads the last request byte.
Usually, more than one byte is read or written in one I/O operation, but a single-byte I/O is sufficient to stop these latency timers. Only HTTP-level bytes can stop the timers. Low-level content exchanged during TCP or SSL handshakes and negotiations has no effect. These stats are collected for basic transactions only.