--MimeMultipartBoundary
Content-Type: TEXT/PLAIN; charset=US-ASCII
On Tue, 19 May 1998, Chris Wedgwood wrote:
> Although, the squid config. that comes with beta20 has memory_pools on and
> no size set, so it defaults to zero with is treated as 2GB, which mean its
> will grow and grow and grow if you leave this part of the config. unedited.
It is not supposed to grow indefinitely. The default (unlimited size)
settings are _intentional_. Memory pools recycle "unused" memory. It is hard
to guess in advance how much of unused memory your cache will have. The
amount depends on the load and access patterns a lot. Thus, by not specifying
the limit in squid.conf, one allows Squid to find out the actual limit.
Again, the amount of idle memory is not supposed to grow indefinitely. If it
does, there is a bug (not even a memory leak!) and it must be isolated
and fixed.
The amount of "busy" or "used" memory reported by cachemgr.cgi in "Memory
Utilization" section does not depend on memory pools settings. If the amount
of _used_ memory grows indefinitely, there is a memory leak and it must be
isolated and fixed.
If neither used nor idle memory grows according to cachemgr.cgi, but the
process size increases, then it is either memory leak for object(s) not
accounted in memory pools or a problem external to Squid (e.g. libc).
Alex.
--MimeMultipartBoundary--
Received on Tue Jul 29 2003 - 13:15:49 MDT
This archive was generated by hypermail pre-2.1.9 : Tue Dec 09 2003 - 16:11:47 MST