Re: [squid-users] Seemingly incorrect behavior: squid cache getting filled up on PUT requests

What is the authoritative source of cache statistics? The slots
occupied due to PUT requests (as suggested by mgr:storedir stats is
quite concerning.
Is there some additional config that needs to be added to ensure that
PUTs are simply bypassed for caching purpose.

NOTE: fwiw, I have verified that subsequent GETs for the same objects
after PUTs do get a cache MISS.

On Sun, Feb 16, 2014 at 3:45 PM, Rajiv Desai <rajiv_at_maginatics.com> wrote:
> On Sun, Feb 16, 2014 at 3:39 PM, Amos Jeffries <squid3_at_treenet.co.nz> wrote:
>> On 17/02/2014 11:41 a.m., Rajiv Desai wrote:
>>> I am using Squid Cache:
>>> Version 3.HEAD-20140127-r13248
>>>
>>> My cache dir is configured to use rock (Large rock with SMP):
>>> cache_dir rock /mnt/squid-cache 256000 max-size=4194304
>>>
>>> My refresh pattern is permissive to cache all objects:
>>> refresh_pattern . 129600 100% 129600 ignore-auth
>>>
>>> I uploaded 30 GB of data via squid cache with PUT requests.
>>> From storedir stats(squidclient mgr:storedir) it seems like each PUT
>>> is occupying 1 slot in rock cache.
>>>
>>> Is this a known bug? PUT requests should not increase cache usage right?
>>>
>>>
>>> Stats:
>>>
>>> by kid9 {
>>>
>>> Store Directory Statistics:
>>>
>>> Store Entries : 53
>>>
>>
>>
>> How may objects in that 30GB of PUT requests?
>>
>> That 53 looks more like the icons loaded by Squid for use in error pages
>> and ftp:// directory listings.
>>
>
> 572557 objects were uploaded with PUT requests.
> I was looking at current size and used slots to interpret current
> cache occupancy. Perhaps I am interpreting these incorrectly?
>
> Current Size: 8960416.00 KB 4.27%
> Current entries: 560025 4.27%
> Used slots: 560025 4.27%
>
>> Amos
>>
Received on Mon Feb 17 2014 - 07:07:17 MST