[squid-users] How to analyse squid memory usage

Dan Charlesworth dan at getbusi.com
Tue May 24 05:44:06 UTC 2016


Gentle bump 😁

-------------- next part --------------
A non-text attachment was scrubbed...
Name: normal-mem.tsv
Type: text/tab-separated-values
Size: 18774 bytes
Desc: not available
URL: <http://lists.squid-cache.org/pipermail/squid-users/attachments/20160524/9c4995c0/attachment-0002.tsv>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: leaky-mem.tsv
Type: text/tab-separated-values
Size: 17652 bytes
Desc: not available
URL: <http://lists.squid-cache.org/pipermail/squid-users/attachments/20160524/9c4995c0/attachment-0003.tsv>
-------------- next part --------------

> On 12 May 2016, at 11:37 AM, Dan Charlesworth <dan at getbusi.com> wrote:
> 
> I’ve now got mgr:mem output from a leaky box for comparison but I’m having a hard time spotting where the problem might be.
> 
> Would anyone more experienced mind taking at these and seeing if anything jumps out as a source of the high memory usage?
> 
>  - The leaky example has 8GB of server memory and 5.7GB was allocated to squid when the snapshot was taken.
> 
>  - The normal example has 12GB of server memory and 2.9GB was allocated to Squid when the snapshot was taken.
> 
> <leaky-mem.tsv><normal-mem.tsv>
> 
> Thanks!
> 
>> On 11 May 2016, at 2:37 PM, Dan Charlesworth <dan at getbusi.com> wrote:
>> 
>> Thanks Amos -
>> 
>> Not sure how self-explanatory the output is, though.
>> 
>> I’ve attached the output from a site with a 12GB server where top was showing 2.9GB allocated to squid (this is normal e.g. “the control"). But the mem output shows the allocated total as ~1GB, apparently?
>> 
>> Maybe things will become clearer once I have a “leaky” server’s output to compare with it.
>> 
>> <bdc-mem.tsv>
>> 
>>> On 10 May 2016, at 6:02 PM, Amos Jeffries <squid3 at treenet.co.nz> wrote:
>>> 
>>> On 10/05/2016 2:35 p.m., Dan Charlesworth wrote:
>>>> A small percentage of deployments of our squid-based product are using oodles of memory—there doesn’t seem to be a limit to it.
>>>> 
>>>> I’m wondering what the best way might be to analyse what squid is reserving it all for in the latest 3.5 release?
>>>> 
>>>> The output of squidclient mgr:cache_mem is completely incomprehensible to me.
>>> 
>>> Try mgr:mem report. It is TSV (tab-separated values) file format.
>>> 
>>> squidclient mgr:mem > mem.tsv
>>> 
>>> ... and load mem.tsv using your favourite spreadsheet program. The
>>> column titles should then be self-explanatory.
>>> 
>>> Amos
>>> 
>>> _______________________________________________
>>> squid-users mailing list
>>> squid-users at lists.squid-cache.org
>>> http://lists.squid-cache.org/listinfo/squid-users
>> 
> 



More information about the squid-users mailing list