diff --git a/benchmarks.md b/benchmarks.md index 5be8734..df52d9d 100644 --- a/benchmarks.md +++ b/benchmarks.md @@ -3,7 +3,7 @@ Collection of hints and links which can be useful for people new to DNS benchmarking. -### Step 0. Prerequisites +## Step 0. Prerequisites See DNS-OARC 42, DNS Benchmarking 101: Essentials and Common Pitfalls [slides](https://indico.dns-oarc.net/event/48/contributions/1033/attachments/991/1943/pspacek.pdf), [video recording](https://www.youtube.com/watch?v=ZrMLeyu4gTU&list=PLCAxS3rufJ1fHh8oe9UQ0IwlVfHq30_hh&index=16) - Test design **must be** different for any combination of @@ -26,7 +26,8 @@ See DNS-OARC 42, DNS Benchmarking 101: Essentials and Common Pitfalls [slides](h - pick minimum value from (# of CPUS in the chosen NUMA domain, number of network queues) and use that for number of threads - these are just a starting point, experiment! -### Resolvers + +## Resolvers - An example with explanation why and how we test resolvers: https://www.isc.org/blogs/bind-resolver-performance-july-2021/ - **:warning: Results cannot be generalized to other data sets** or setups with any certainty - Why? Because every single query (and it's timing) changes _state_ of the system under test. Not to speak of dependency on authoritative server performance ...