Heinz Diehl wrote:
Hi,
given the following settings in squid.conf (2.7-STABLE9):
cache_mem 512 MB
maximum_object_size_in_memory 10 MB
memory_replacement_policy heap GDSF
cache_replacement_policy heap LFUDA
cache_dir coss /var/cache/squid/cs 10240 max-size=131072 block-size=4096 maxfullbufs=10
cache_dir aufs /var/cache/squid/A 20000 64 256 min-size=131073
minimum_object_size 0 KB
maximum_object_size 200 MB
When someone downloads e.g. "patch-2.6.35-git10.bz2" with a size of ca. 6.4 MB,
I see a SWAPOUT for this file in the logs, and the next one downloading
this file is served directly and entirely from the cache (disk), I see a
TCP_HIT in the logs. So far, so good.
My question is: why is that file not getting cached in memory? The
maximum_object_size_in_memory is 10 MB and big enough.
For testing purposes, I set up a squid proxy with cache_dir "null", the
log files show RELEASE for the mentioned kernel patchfile directly after
downloading, and it is never cached in memory either...
What am I missing here?
Did the object arrive with known content-size header?
In the absence of a known content size that can be used to determine its
best caching position Squid will be conservative and assume it's going
to be a huge ISO or DVD sized thing. Causing a disk save.
Amos
--
Please be using
Current Stable Squid 2.7.STABLE9 or 3.1.6
Beta testers wanted for 3.2.0.1
