Search squid archive

Re: Squid 3.3 is very aggressive with memory

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 01/09/2014 11:41 PM, Nathan Hoad wrote:
> Alright, it took me a little longer to get information than I
> anticipated, but here it is. I can confirm that this is related to
> HTTPS inspection.
> 
> I started by running the second instance with only transparent HTTP,
> letting the first instance take care of HTTPS as I mentioned earlier.
> In this situation, the second instance memory never grew higher than
> 40mb, but the first still grew as expected. I then switched it around,
> and ran the second instance serving only transparent HTTPS and a very
> minimal config, and the second is now the one that grows. The first
> one still grows, but I suspect this is due to direct proxy SSL bump,
> memory pools and caching being enabled.


Hi Nathan,

    Do you think the following bug may be a factor?

  http://bugs.squid-cache.org/show_bug.cgi?id=4005

Setting dynamic_cert_mem_cache_size to zero would be a good next triage
step, I guess.


HTH,

Alex.





[Index of Archives]     [Linux Audio Users]     [Samba]     [Big List of Linux Books]     [Linux USB]     [Yosemite News]

  Powered by Linux