Hacker News Reader

This is a good writeup but why bother with limits at all? Except core pinning there should be no gain in setting limits for non-metered workloads and it’s most likely just letting compute go unused. As far as I can tell this kernel change just fixes the tail latency problem

View on HN

From my understanding the other goal that is often overlooked is that limiting resources on unmetered workloads prevents those processes from depriving others (and the host) of resources. It's mostly just a catch-all situation, but I would expect there to be ways to fine-tune this behavior.

This is not the case if you set cpu request the kubelet (actually cri) will configure cpu.shares controller

Reply on news.ycombinator.com