[squid-users] Squid 3.5.7, cache_swap_high, bug or not bug ?
squid3 at treenet.co.nz
Tue Aug 18 17:51:28 UTC 2015
On 19/08/2015 4:39 a.m., Stakres wrote:
> Hi All,
> I'm facing a weird situation with a squid *3.5.7*, have a look:
> Store Directory #0 (aufs): /cachesdg/spool
> FS Block Size 4096 Bytes
> First level subdirectories: 16
> Second level subdirectories: 256
> Maximum Size: 67108864 KB
> Current Size: 66288408.00 KB
> *Percent Used: 98.78%*
> Filemap bits in use: 7858031 of 8388608 (94%)
> Filesystem Space in use: 63582908/575775620 KB (11%)
> Filesystem Inodes in use: 7428375/36569088 (20%)
> Flags: SELECTED
> Removal policy: lru
> LRU reference age: 1.06 days
> In the squid.conf:
> cache_swap_low 75
> cache_swap_high *80*
> Is that normal ?
Maybe. Depends on your traffic speed and cache_dir capacity. If its
arriving faster than the garbage colection can purge objects then it
could get very high.
> I should see the Squid cleaning objects to respect the 80% swap high, am I
> wrong ?
Its been a very long time since I looked at teh code in this area and
cant check it right now. But IIRC this is the intended behaviour:
* Below swap_high you should see only turnover from objects being updated.
* Above swap_high you should see hourly purges down to swap_low.
But there is also <http://bugs.squid-cache.org/show_bug.cgi?id=3553>
nobody has followed up on yet.
More information about the squid-users