named out of swap on NetBSD/amd64

[Greg Choules]

Point taken. Unique does not necessarily mean non-existent and *something*
will end up in cache. So restricting your max-cache-size would seem to be
the thing for you. If it were my server, I would monitor just how much RAM
is getting used in total and adjust max-cache-size to allow BIND to use as
much RAM as you can afford. That way you minimise the frequency of cache
cleaning, which is an overhead.

Greg

On Wed, 15 Feb 2023 at 19:45, Jan Schaumann via bind-users <
bind-users at lists.isc.org> wrote:

> Greg Choules <gregchoules+bindusers at googlemail.com> wrote:
>
> > Since the queries are unique the responses should be NXDOMAIN
>
> Well, _some_ of them will be NXDOMAIN, many others
> will be NOERROR or NODATA etc., no?  But yes, they all
> ended up contributing to the cache growing, and it
> seems that 90% of physical memory all in use by bind
> was simply more than my system could handle, as it
> wanted to do some other work as well. :-)
>
> -Jan
> --
> Visit https://lists.isc.org/mailman/listinfo/bind-users to unsubscribe
> from this list
>
> ISC funds the development of this software with paid support
> subscriptions. Contact us at https://www.isc.org/contact/ for more
> information.
>
>
> bind-users mailing list
> bind-users at lists.isc.org
> https://lists.isc.org/mailman/listinfo/bind-users
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.isc.org/pipermail/bind-users/attachments/20230215/24a21986/attachment-0001.htm>