Re: [squid-users] squid 3.2: TCP_MISS:HIER_DIRECT

On 12/04/2012 11:36 p.m., David Touzeau wrote:
> Dear
>
>
> With this configuration i have a lot of TCP_MISS:HIER_DIRECT
>
> I understand that TCP_MISS means that the object is not stored on cache
>
> What's means HIER_DIRECT ?

http://wiki.squid-cache.org/SquidFaq/SquidLogs under hierarchy codes.

>
> Second, why the proxy did not cache anything ?

Guessing based on the below. You have dedicated (non-shared) caches. Two
identical requests going to the proxy can be served by different
workers, and thus both be MISS. There is also the possibility that they
were different variants being requested, or explicitly not cacheable
responses. Its hard to tell without full details about what requests and
responses you mean by "anything".

>
> cache_dir diskd /var/squid/cache_booster 500 16 256 max-size=322560

You probably want to try the "rock" cache_dir type as your booster for
small objects.

> #--------- Multiple cpus -- (enabled)
> workers 4
> if ${process_number} = 1
> cache_dir aufs /var/cache/squid2-1 5000 128 512 min-size=322560
> endif
> if ${process_number} = 2
> cache_dir aufs /var/cache/squid2-2 5000 128 512 min-size=322560
> endif
> if ${process_number} = 3
> cache_dir aufs /var/cache/squid2-3 5000 128 512 min-size=322560
> endif
> if ${process_number} = 4
> cache_dir aufs /var/cache/squid2-4 5000 128 512 min-size=322560
> endif

Better config:

   cache_dir aufs /var/cache/squid2-${process_number} 5000 128 512
min-size=322560

> #------------------
Received on Fri Apr 13 2012 - 07:11:46 MDT