Farzad Fallah wrote:
Hi,
I am running a proxy-only squid 3.0 Stable 8 ( no caching ) , but after
sometime squid memory usage starts to increase. why should it consume
memory if it is not caching anything ? is there anything wrong with my
config ?
acl manager proto cache_object
hierarchy_stoplist cgi-bin ?
icp_port 0
http_port 192.168.10.1:3128 transparent
cache_dir null /tmp
cache deny all
coredump_dir /var/spool/squid3
access_log /var/log/squid3/access.log squid
dns_nameservers 127.0.0.1 4.2.2.4 192.9.9.3
acl QUERY urlpath_regex cgi-bin \?
no_cache deny QUERY
client_db off
half_closed_clients off
acl localhost src 192.168.10.0/255.255.255.0
Um, "localhost" is not a good name for this ACL.
That name has a special meaning in networking as the 127.0.0.0/8 range,
which is handled specially on NIC.
I like to recommend localnet for this, others prefer our_networks.
Something to refer to the internal LAN range.
acl CONNECT method CONNECT
http_access allow localhost
http_access allow CONNECT
http_access deny all
Regards
Squid consumes memory for all sorts of things. Cache indexes are only
one (admittedly large) amongst many.
That config shows nothing relating to memory. Though if it is a leak, it
likely won't show there anyway.
Is there any other trace you know how to do that would show memory usage
within an app?
Squid when built with it has valgrind (alleyoop) support, for real-time
leak checks through the cachemgr interface.
Amos
--
Please be using
Current Stable Squid 2.7.STABLE6 or 3.0.STABLE16
Current Beta Squid 3.1.0.8
