@nova TBH shouldn't even be the developers per se, but the underlying runtimes doing it right. For example .net is aware of the cgroups under k8s and just sets it's threadpools up properly, golang on the other hand is of the opinion that every damn CPU core it can see belongs to it, no matter the cgroups - Uber gladly fixed it with a lib: https://github.com/uber-go/automaxprocs

@nova To add to that: One really has to see to believe how hard a process can get throttled - imagine a well parallelized application seeing all 256 threads my k8s workers offer - and then only being allowed 1-2 of those.