The tl;dr is that unless you had an HPC workload with a NUMA box, you couldn't observe this bad behavior.
Which means in reality, you could name approximately everyone that ran into this issue on a single list: top500.org.
Which means in reality, you could name approximately everyone that ran into this issue on a single list: top500.org.
The Linpack benchmark is an example of an HPC code that should run one process per core and be pinned.
We didn't have HPC workloads, just Postgres, which uses one OS process per connection, and performance was terrible as a result.
I'd bet, but not too much, that that was more due to a) postgres' internal locking implementation scaling horribly at that time b) zone_reclaim_mode leading to bad behaviour around IO.
It's really hard to find a decent article on the subject, here's two of the best I've found. https://www.mssqltips.com/sqlservertip/4403/understanding-sq... https://docs.microsoft.com/en-us/sql/relational-databases/th...