Squid_ The Definitive Guide - Duane Wessels [149]
Connection: 0x84ecd10
FD 132, read 1273, wrote 12182
FD desc: http://www.squid-cache.org/Doc/FAQ/FAQ.html
in: buf 0xa063000, offset 0, size 4096
peer: 206.168.0.9:1058
me: 192.43.244.42:3128
nrequests: 3
defer: n 0, until 0
uri http://www.squid-cache.org/Doc/FAQ/FAQ.html
log_type TCP_MISS
out.offset 0, out.size 0
req_sz 392
entry 0x960c680/3B49762ABF444D80B6465552F6CFAD4C
old_entry 0x0/N/A
start 1066036250.669955 (2.240814 seconds ago)
Connection
The internal memory address of the connection structure.
FD
The file descriptor for the TCP connection, followed by the number of bytes read and written.
FD desc
A short description of the socket, usually a URI. This is the same as in Section 14.2.1.25.
in
The internal memory location of the input buffer, the offset at which Squid will place data after the next read( ) call, and the size of the input buffer.
peer
The remote socket address of the TCP connection. You can correlate this value with what you see in netstat -n output.
me
The local socket address of the TCP connection.
nrequests
The number of HTTP requests received on this connection. A value greater than 1 indicates persistent connection reuse.
defer
Indicates whether Squid is postponing reads on the socket.
uri
The URI from the client's request. Unlike FD desc, this one isn't truncated.
log_type
The cache status code that appears in access.log when this transaction is complete.
out.offset
The offset, relative to the start of the HTTP reply message, in which the client side has requested data from the storage system.
out.size
The number of response bytes written to the client.
req_sz
The size of the client's HTTP request. Note, for persistent connections, this refers only to the current request.
entry
The memory address and MD5 hash of the corresponding StoreEntry structure.
old_entry
For validation requests, this is the memory address and MD5 hash of the cached response StoreEntry.
start
The time at which Squid began processing this request.
store_digest: Store Digest
This page is available only with the ./configure —enable-cache-digests option. It displays a few statistics about Squid's own cache digest. It looks like this:
store digest: size: 620307 bytes
entries: count: 324806 capacity: 992490 util: 33%
deletion attempts: 0
bits: per entry: 5 on: 1141065 capacity: 4962456 util: 23%
bit-seq: count: 1757902 avg.len: 2.82
added: 324806 rejected: 611203 ( 65.30 %) del-ed: 0
collisions: on add: 0.08 % on rej: 0.07 %
size
The number of bytes that the digest occupies in memory.
entries count
The number of cached objects entered into the digest.
entries capacity
The target capacity for the digest. Note, this isn't a hard limit, but rather an estimate for optimally sizing the digest.
entries util
The percentage of entries added compared to the capacity.
deletion attempts
Squid doesn't currently support deletion of cache digest entries, so this is always zero.
bits per entry
The number of bits that each item turns on. The same as the digest_bits_per_entry value from squid.conf.
bits on
The number of bits that have been turned on so far.
bits capacity
The total number of bits in the digest. Equal to the digest size multiplied by eight.
bit-seq count
The number of same-bit sequences in the digest. For example, the pattern 110100011111 has 5 sequences of 1s and 0s.
bit-seq avg.len
The mean length of same-bit sequences.
added
The number of entries added to the digest since it was created.
rejected
The number of entries not added to the digest. An entry may not be added because it isn't cachable, is too large, stale, or about to become stale, etc.
del-ed
Squid doesn't currently support deletion of cache digest entries, so this is always zero.
collisions on add
This is the percentage of additions