Search squid archive

Re: seemingly stupid question about cache_dir and TCP_HIT

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Tue, 15 Dec 2009 11:06:40 -0500, "B. Cook"
<bcook@xxxxxxxxxxxxxxxxxxxxxxx> wrote:
> Trying to setup a small local proxy for testing..
> 
> 2.7 Stable7 on FreeBSD 32bit
> 
> here are the mem and cache entries from squid.conf..
> 
> # memory options
> memory_pools off
> cache_mem 1024 MB
> maximum_object_size_in_memory 2 MB
> 
> ## cache options
> cache deny all
> cache_dir null /tmp
> cache_access_log /var/log/squid/access.log
> cache_store_log none
> cache_log /var/log/squid/cache.log
> cache_mem 1024 MB
> no_cache deny nocache
> cache_effective_group squid
> cache_effective_user squid
> 
> in short the TCP_HIT *never* happens..
> 
> 341843 /var/log/squid/access.log
>   60M	/var/log/squid/access.log
> 
> and the log is rotated daily.. so we are using the proxy *heavily*..
> 
>  > grep -c TCP_HIT /var/log/squid/access.log
> 0
> 
>  > grep -c TCP_MISS /var/log/squid/access.log
> 327072
> 
> is it because I have the cache_dir disable the reason for the 0
TCP_HITs?

Sort of, but not in the way you think...

 "cache deny all"  prevents any things being stored by Squid.

 *_HIT is something being taken from existing storage for a client.

Add the two together...

Amos


[Index of Archives]     [Linux Audio Users]     [Samba]     [Big List of Linux Books]     [Linux USB]     [Yosemite News]

  Powered by Linux