MicrosoftI ran into a really bizarre piece of behavior with PsExec... When configuring a Threadripper PRO 5975WX in the 4x NUMA node mode with L3 as SRAT, one of my non-numa-aware pieces of software (Ultra Fractal) was defaulting to the 4th node most of the time, only giving itself access to 16 cores. If I forced it to the first node, it would still only use 32/64 cores; affinity couldn't be set to all-core because the program itself (as verified with the author) was only using a 32-bit affinity mask.
Since the initial node assignment was unpredictable I decided to use PSExec to run it on the local machine and force it to start on the first CPU and at least get 32 cores reliably, and oddly enough it ran with affinity on 63/64 cores across the 4 nodes. This is on Windows 10 Pro Workstation so the kernel patches of Win 11 that auto-distribute weren't there. Seemed very odd. Additionally when I eventually turned off the L3 as SRAT feature for now due to lack of software that cared about NUMA (except x265, which works just as well without it) and ran with the old shortcut, the affinity was locked to the first core instead. Not sure why this happened but it was a good workaround. It would be interesting to see results from software like this from a 64/128 core system on Windows 10 with CPU groups or a system with two physical CPUs.
