NUMA only helps when you have separate processes that each are running in their own NUMA context. This is not the case with MWG, so enabling NUMA won't help here. We have implemented our own strategy of assigning and pinning threads to specific CPUs in order to minimize context switches.
We had some cases of NUMA enabled kernels interacting poorly with certified hardware. That's the reason it is disabled by default on MWG appliances.
Ed, thank for this information.
it is clear now.