Bin Liu wrote:
Thanks for your reply.
# /usr/local/squid/sbin/squid -v
Squid Cache: Version 2.7.STABLE6
configure options: '--prefix=/usr/local/squid' '--with-pthreads'
'--with-aio' '--with-dl' '--with-large-files'
'--enable-storeio=ufs,aufs,diskd,coss,null'
'--enable-removal-policies=lru,heap' '--enable-htcp'
'--enable-kill-parent-hack' '--enable-snmp' '--enable-freebsd-tproxy'
'--disable-poll' '--disable-select' '--enable-kqueue'
'--disable-epoll' '--disable-ident-lookups' '--enable-stacktraces'
'--enable-cache-digests' '--enable-err-languages=English'
The squid process grows without bounds here. I've read the FAQ, and
tried lowering cache_mem setting, decreasing cache_dir size. That
server has 4GB physical memory, and with total cache_dir size setting
to 60G, squid resident size still can grow beyond bound and start
eating swap.
Note that cache_mem is not a bound on squid memry usage. Merely the RAM
cache_dir.
The OS is FreeBSD 7.1-RELEASE.
Thanks.
Do you have access to any memory-tracing software (valgrind or similar?)
tracking an actual memory usage while live can be done when built
against valgrind and certain cachemgr reports. I'll have to look them up.
Amos
--
Please be using
Current Stable Squid 2.7.STABLE6 or 3.0.STABLE14
Current Beta Squid 3.1.0.7
