18 Bře
2018
18 Bře
'18
14:39
Hi Klaus,
Thanks for the feedback. As I wrote before, if the virtual memory
consumption
is an issue, there are some configuration options which could help. You
could
also disable zone journaling at all. However, the peak memory
consumption
still depends on other factors (zone transfers, DDNS, DNSSEC
signing,...).
Now we are working on outgoing IXFR optimization, which is a bit greedy
if the changes are huge.
Best,
Daniel
On 2018-03-18 14:02, Klaus Darilion wrote:
Just some comments from a user: It is hard to guess if
the consumed
memory is something to care or not. I do not know if all the virtual
memory may be used and some time may cause problems. If my monitoring
tells me "100 % memory used" I am concerned, as I do not know if this
is a real problem or just some irrelevant buffers. Also I do not know
how the name server will behave when running out of memory (crash,
serving old data, serving broken data, ...). Hence, I have to add more
memory or choose a different name server.
I have a server with limited memory. NSD was running out of memory. So
I tried Knot. Knot consumed similar memory (from a non-developer view,
not capably of analyzing virtual vs resistent vs ... memory).
So, I switched the Bind and was happy because my monitoring now tells
me "50% memory used" - and I am not worried about memory anymore.
Sometimes I have time to investigate and analyze problems, but most of
the time I do not have time for debugging and just need a solution for
my problem, hence I still use Bind on this server.
Regards
Klaus