On 3/3/19 9:39 PM, George Xie wrote:
Squid version: 3.5.23-5+deb9u1
debian 9, currently stable, soon to be replaced by debian 10, containing
squid-4.4
http_port 127.0.0.1:3128
cache deny all
access_log none
On 04.03.19 09:34, Alex Rousskov wrote:
Unfortunately, this configuration wastes RAM: Squid is not yet smart
enough to understand that you do not want any caching and may allocate
256+ MB of memory cache plus supporting indexes. To correct that default
behavior, add this:
cache_mem 0
this should help most.
Furthermore, older Squids, possibly including your no-longer-supported
version
its supported, just not by squid developers. There are many SW distributions
that try to support software for longer than just a few weeks/months, e.g
during whole few-year release cycle.
might explain why you see your Squid allocating a 392 MB table.
If you want to know what is going on for sure, then configure malloc to
dump core on allocation failures and post a stack trace leading to that
allocation failure so that we know _what_ Squid was trying to allocate
when it ran out of RAM.
--
Matus UHLAR - fantomas, uh...@fantomas.sk ; http://www.fantomas.sk/
Warning: I wish NOT to receive e-mail advertising to this address.
Varovanie: na tuto adresu chcem NEDOSTAVAT akukolvek reklamnu postu.
The early bird may get the worm, but the second mouse gets the cheese.
_______________________________________________
squid-users mailing list
squid-users@lists.squid-cache.org
http://lists.squid-cache.org/listinfo/squid-users
