Hi Thomas On Mon, Oct 13, 2014 at 02:31:37PM -0400, Thomas Schulz wrote: > I restarted bind 9.9.6 with a max-cache-size of 30M. We have 3 views. > The inital process size was 36 MB. The process grew to 184 MB. It grew > to 596 MB without the max-cache-size being set and was still growing > when I restarted it. BUT when I now do an rndc dumpdb -cache, the
max-cache-size affects the size of an internal memory context that's
used for cache. But the process size is made up of all the memory the
program uses (its various memory contexts, memory used outside contexts
such as by libraries used by BIND, direct allocations, BSS and other
maps).
If you want to check how much memory is used by the cache, and if it
goes above max-cache-size, enable the statistics channels in the named
configuration and dump XML statistics to look at the usage for the
"cache" contexts.
If you have max-cache-size set, any unchecked growth above it of the
"cache" contexts is a bug. But don't compare max-cache-size against the
process size. Other parts of the process apart from the cache use memory
too.
Also as Jeremy asked, you may want to share your named configuration
with us so we can check it.
Mukund
pgpGvc4x_Tf1_.pgp
Description: PGP signature
_______________________________________________ Please visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe from this list bind-users mailing list bind-users@lists.isc.org https://lists.isc.org/mailman/listinfo/bind-users
