Hi Samuel Miller - Thanks for reading and reaching out. I rewrote these articles because of all the different information out there. Generally this (and the 2019 article) should be your go to. Here's a few responses to your questions:
- NUMA - Most systems today do not need to concern themselves with tuning/modifying the RSS/VMQ NUMA configuration on the system. The defaults will suffice.
- In 2016, you must modify the base processor to avoid CPU0. In 2019 you can optionally do this as well (assuming that Dynamic VMMQ is configured on your system which may alleviate this problem). Even in 2019 safest approach is to modify the base proc to avoid CPU0.
- Assuming you're using Switch Embedded Teaming (e.g. Server 2016 or higher) you no longer need to concern yourselves sum-of-queues, overlapping processors, (and 99% of cases) spanning numa nodes. LBFO (which has been deprecated for Azure Stack HCI in the future) is a different story.
Microsoft