> ... /etc/resolv.conf ... ...
> ...don't edit this file manually it is auto-generated ...
I have been trying not to comment on any of this discussion, but You just hit a nerve for me (in a good way!).
resolv.conf: near and dear to my heart
Don't edit manually...: if it is cattle (most servers and IoT) - ok, I move on. If it is a pet (any of my main laptops), whoa. Stop what I'm doing and track down the software that did this. Purge it or re-write the offending code to not mess with stuff. Track down what was relying on this behaviour and purge. Rinse, repeat.
FWIW, I am running Slackware, OpenBSD, and sometimes FreeBSD on my pets (they are all installed it's just that I mostly live in the first two). Also, I find it hard to not have all the different man pages always available (no, I don't have a constant Internet connection - Security policies).
i.e this year Lamborghini might be faster than a Ferrari... Next year they might swap. But no one will say Lamborghini or Ferrari are slow.
My humble point,unless absolute throughput (Then you looking at userland tcp-stack anyway) is your absolute goal. Things like tools,skillset, environment, community might play a bigger role. Yea i still love Freebsd but uses Linux on Desktop daily. Freebsd just kinda 'fits-in-your-head'
Linux: I miss the simple days when you could edit files like /etc/resolv.conf for nameservers :)
These days i see quite a few "don't edit this file manually it is auto-generated messages" :/