Re: [squid-users] question in cache Manager about # of clients and # of hits http

From: Amos Jeffries <squid3_at_treenet.co.nz>
Date: Tue, 30 Jul 2013 20:36:48 +1200

On 30/07/2013 7:31 p.m., Ahmad wrote:
> hi ,
> i have Squid Cache: Version 3.1.6
> ============
> i have squidclient installed on .
>
> here is the result from squidclient :
> HTTP/1.0 200 OK
> Server: squid
> Mime-Version: 1.0
> Date: Tue, 30 Jul 2013 07:18:45 GMT
> Content-Type: text/plain
> Expires: Tue, 30 Jul 2013 07:18:45 GMT
> Last-Modified: Tue, 30 Jul 2013 07:18:45 GMT
> X-Cache: MISS from dft
> X-Cache-Lookup: MISS from dft:22001
> Via: 1.0 dft (squid)
> Proxy-Connection: close
>
> Squid Object Cache: Version 3.1.6
> Start Time: Sun, 28 Jul 2013 13:37:00 GMT
> Current Time: Tue, 30 Jul 2013 07:18:45 GMT
> Connection information for squid:
> *Number of clients accessing cache: 2211
> Number of HTTP requests received: 80437449*
> Number of ICP messages received: 0
> Number of ICP messages sent: 0
> Number of queued ICP replies: 0
> Number of HTCP messages received: 0
> Number of HTCP messages sent: 0
> Request failure ratio: 0.00
> Average HTTP requests per minute since start: 32152.5
> Average ICP messages per minute since start: 0.0
> Select loop called: 2096328654 times, 0.072 ms avg
> Cache information for squid:
> Hits as % of all requests: 5min: 44.1%, 60min: 43.4%
> Hits as % of bytes sent: 5min: 36.8%, 60min: 38.6%
> Memory hits as % of hit requests: 5min: 18.3%, 60min: 16.9%
> Disk hits as % of hit requests: 5min: 45.3%, 60min: 43.1%
> Storage Swap size: 272496340 KB
> Storage Swap capacity: 98.6% used, 1.4% free
> Storage Mem size: 1014520 KB
> Storage Mem capacity: 100.0% used, 7276133255119654.0% free
> Mean Object Size: 108.79 KB
> Requests given to unlinkd: 0
> Median Service Times (seconds) 5 min 60 min:
> HTTP Requests (All): 0.07014 0.07014
> Cache Misses: 0.19742 0.19742
> Cache Hits: 0.00000 0.00000
> Near Hits: 0.64968 0.20843
> Not-Modified Replies: 0.00000 0.00000
> DNS Lookups: 0.06083 0.06364
> ICP Queries: 0.00000 0.00000
> Resource usage for squid:
> UP Time: 150104.835 seconds
> CPU Time: 105900.170 seconds
> CPU Usage: 70.55%
> CPU Usage, 5 minute avg: 58.96%
> CPU Usage, 60 minute avg: 52.03%
> Process Data Segment Size via sbrk(): 4192192 KB
> Maximum Resident Size: 16999120 KB
> Page faults with physical i/o: 89
> Memory usage for squid via mallinfo():
> Total space in arena: -1980 KB
> Ordinary blocks: -165956 KB 453500 blks
> Small blocks: 0 KB 0 blks
> Holding blocks: 66172 KB 15 blks
> Free Small blocks: 0 KB
> Free Ordinary blocks: 163975 KB
> Total in use: -99784 KB -154%
> Total free: 163975 KB 255%
> Total size: 64192 KB
> Memory accounted for:
> Total accounted: -1252542 KB -1950%
> memPool accounted: -1252542 KB -1950%
> memPool unaccounted: 1316733 KB 2051%
> memPoolAlloc calls: 12
> memPoolFree calls: 22462254711
> File descriptor usage for squid:
> Maximum number of file descriptors: 65536
> Largest file desc currently in use: 34282
> Number of file desc currently in use: 23259
> Files queued for open: 0
> Available number of file descriptors: 42277
> Reserved number of file descriptors: 100
> Store Disk files open: 11827
> Internal Data Structures:
> 2547268 StoreEntries
> 157597 StoreEntries with MemObjects
> 156565 Hot Object Cache Items
> 2504776 on-disk objects
>
>
>
>
>
> =============================================
>
> as we see above , we have :
> *Number of clients accessing cache: 2211*
>
> does that mean that i have 2211 single ips accessing squid ??
> i checked from my side " from my router " , i found my real clients access
> squid is about 1580 , so why it is greater that 1580 ????

Did you check both IPv6 and IPv4 clients?

> does this value count the Natting in routers as new clients ??

Only if they reach Squid as identifiably different IPs.

> i mean does this value accurate ? or it count # of ips in a range of time
> ???

It is the count of distinct IPs currently in the client-DB.

The client-DB is the set of distinct IPs connected to your Squid from
any direction (both LAN and WAN) over a period of up to 24hrs. They are
"faded" / aged out of the DB dynamically based on several factors
including last access and frequecy of access when the client-DB garbage
collector gets run to remove old entries.

Amos
Received on Tue Jul 30 2013 - 08:36:53 MDT

This archive was generated by hypermail 2.2.0 : Tue Jul 30 2013 - 12:00:27 MDT