Re: questions how NSD slave handles XFR and how to improve XFR-patching performance

Wouter Wijngaards <[email protected]> Mon, 8 Apr 2019 09:29:30 +0200

Newsgroups	gmane.network.dns.nsd.general
Message-ID	<[email protected]>

Hi Klaus, Anand,

On 4/8/19 8:57 AM, Anand Buddhdev wrote:
> On 04/04/2019 23:07, Klaus Darilion wrote:
> 
> Good morning Klaus!
> 
> [snip]

One way to speed up applying xfrs is to change the xfr directory to a
memory mapped file system, like /tmp.  It could be /usr/local/var/tmp
which is disk-based, and with a memory file system there is no disk
access needed.  It uses memory, then.  There is an option in nsd.conf to
change it, xfrdir: "/path" .

Best regards, Wouter

> 
>> Any ideas to improve the XFR-applying-speed? I think the most time
>> consuming part is the clone() (P2 has around 2.3million page tables).
>> Are there and config/build options to improve this? Ie huge pages? Using
>> some other forking function?
> 
> I can't comment on improving NSD's XFR-handling model, but you could
> throttle it by setting a larger value for "xfrd-reload-timeout" in
> nsd.conf. The default is 1 second, but if you set it to something like
> 30 seconds, then NSD will receive and apply the XFRs received, but only
> reload once every 30s, and allow the server some breathing room.
> 
> Regards,
> Anand Buddhdev
> RIPE NCC
> _______________________________________________
> nsd-users mailing list
> [email protected]
> https://open.nlnetlabs.nl/mailman/listinfo/nsd-users
>

_______________________________________________
nsd-users mailing list
[email protected]
https://open.nlnetlabs.nl/mailman/listinfo/nsd-users

signature.asc (application/pgp-signature, 833 B)