We solved that by sharding customers, so about every 1000 database clusters got their own k8s cluster; production then could run hundreds of those “orchestras”, but we could afford to load test one of them and be relatively confident the test was valid for production.
This relied on the various cloud vendors running the front-line load balancers that took traffic and moved it into the shards though. I was about to say that seemed to be the case for Microsoft here as well, but actually it seems they load tested an individual server with different specs than prod.
Tricky problem though - it seems they reasoned if a lower specced server passed the load test, a much beefier prod server would handle the load too. Wrong, but you can see why someone made that assumption.
I doubt this very much.
The load testing env is the Office 365 load testing environment. I'd be surprised if it is less than 10,000 cores, and the machines are probably good but older; possibly 50 core Xeons instead of 128 core EPYC or something.
It seems likely that the test env was setup to mirror one of the smaller 365 regions a few years ago and the only updates were when machines were replaced.
I've seen NUMA cache line contention affecting us for real (on Windows, for our game tools). Limiting certain tools to run locked under one NUMA node helped a lot. It's real.
The updated CoreInfo https://learn.microsoft.com/en-us/sysinternals/downloads/cor... shows this well
But if low is 64 and high is a whole cluster, now that's a different kind of maths.