Hi,
Looking at some stats from Cache Manager. I originally
thought there were just hits or misses, is a Near Hit
still a miss? I am hoping for a deeper explaination of
Near Hits. Also, can you guys tell me, but doesn't
this look like a poorly performing squid server?? It's
for approx 30Hours.
Connection information for squid:
Number of clients accessing cache: 5384
Number of HTTP requests received:
7124911
Number of ICP messages received: 0
Number of ICP messages sent: 0
Number of queued ICP replies: 0
Request failure ratio: 0.00
Average HTTP requests per minute since start:
3641.7
Average ICP messages per minute since start:
0.0
Select loop called: 26095903 times, 4.498 ms
avg
Cache information for squid:
Request Hit Ratios: 5min: 99.1%, 60min:
98.5%
Byte Hit Ratios: 5min: 99.0%, 60min:
98.8%
Request Memory Hit Ratios: 5min: 78.4%,
60min: 91.2%
Request Disk Hit Ratios: 5min: 4.5%,
60min: 4.1%
Storage Swap size: 802820 KB
Storage Mem size: 90464 KB
Mean Object Size: 609.12 KB
Requests given to unlinkd: 0
Median Service Times (seconds) 5 min 60 min:
HTTP Requests (All): 0.00678 0.00379
Cache Misses: 0.03241 0.04776
Cache Hits: 0.00463 0.00379
Near Hits: 169.11253 169.11253
Not-Modified Replies: 0.00000 0.00000
DNS Lookups: 0.00000 0.05078
ICP Queries: 0.00000 0.00000
Resource usage for squid:
UP Time: 117388.930 seconds
CPU Time: 54245.630 seconds
CPU Usage: 46.21%
CPU Usage, 5 minute avg: 42.93%
CPU Usage, 60 minute avg: 38.88%
Process Data Segment Size via sbrk(): 179290
KB
Maximum Resident Size: 0 KB
Page faults with physical i/o: 52592
__________________________________
Do you Yahoo!?
Yahoo! Mail - 250MB free storage. Do more. Manage less.
http://info.mail.yahoo.com/mail_250
