From 73842f727be3976f995e1e2d69c9555673a96594 Mon Sep 17 00:00:00 2001 From: DL6ER Date: Sat, 18 May 2019 13:33:43 +0200 Subject: [PATCH] Add more details for why we set num-threads to 1. The added text has been copied from an Arch Linux page. Signed-off-by: DL6ER --- docs/guides/unbound.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/guides/unbound.md b/docs/guides/unbound.md index 70039eb..10447fe 100644 --- a/docs/guides/unbound.md +++ b/docs/guides/unbound.md @@ -101,7 +101,7 @@ server: # This only applies to domains that have been frequently queried prefetch: yes - # One thread should be sufficient, can be increased on beefy machines + # One thread should be sufficient, can be increased on beefy machines. In reality for most users running on small networks or on a single machine it should be unnecessary to seek performance enhancement by increasing num-threads above 1. num-threads: 1 # Ensure kernel buffer is large enough to not lose messages in traffic spikes