[nsd-users] Consequences of disable-radix-tree
wouter at nlnetlabs.nl
Thu Aug 25 10:19:24 CEST 2016
On 25/08/16 10:15, Anand Buddhdev wrote:
> On 25/08/16 09:31, W.C.A. Wijngaards wrote:
> Hi Wouter,
>>> Could you please tell us more about this? Are lookups in
>>> red-black trees slower? Do they use more CPU? Is there any other
>>> reason why you don't use a red-black tree by default?
>> A small speed difference. It is a memory-for-speed tradeoff, and
>> the benefits are about 10% either way. If memory is an obstacle;
>> 10% speed hopefully isn't. Otherwise, upgrade the machine, I
> Thanks for this explanation. We have enough memory on our servers, so
> I don't foresee the need to disable the radix tree.
> Do you mind appending "but uses some more CPU" to the help string of
> the disable-radix-tree option? This will make the consequences of this
> option completely clear.
Yes, done that! This is the tree for the main lookup (for David:) that
looks for the answer to the query. NSD also uses (various) data
structures for other purposes (including radix and red-black trees) and
those are not changed by the option.
Best regards, Wouter
> nsd-users mailing list
> nsd-users at NLnetLabs.nl
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 819 bytes
Desc: OpenPGP digital signature
More information about the nsd-users