3 ms·
How is this “news”? It was already the case in 2018. Also, no mention of the scheduler overhead. And the maintenance overhead is the worst.
by aairey 3mo ago
How is this “news”?
It was already the case in 2018.
Also, no mention of the scheduler overhead.
And the maintenance overhead is the worst.
- websap 3mo agoScheduler overhead for CPU limits? Are you talking about the Linux Scheduler or the k8s scheduler?
- acuteaura 3mo agoIt's not as much an "overhead" as it will mess up your latency. Limits don't stop you from using available resources until you hit the relative allowance in a CFS window, so a 1 CPU limit on a 32 CPU machine at worst gives you 32 cores for 3.3ms every 100ms.
- ofjcihen 3mo agoMany orgs are just now discovering K8s at scale. Seriously. I’m not sure why that is but a large number of the F100s I contract with are suddenly deploying 4 times the number of containers they had before.
- stanac 3mo agoCould it be that they're using coding agents to develop applications they previously wouldn't spent time on developing? Like internal tools, or experimental builds.
- denysvitali 3mo agoLooks like a bad copy of: https://home.robusta.dev/blog/stop-using-cpu-limits https://home.robusta.dev/blog/stop-using-cpu-limits "For the Love of God, Stop Using CPU Limits on Kubernetes" literally same title