Top all-time · #5369
Robusta
Company blog · home.robusta.dev/blogprogrammingsystemsai
Robusta is the company blog at home.robusta.dev, writing about programming, systems and ai. Since 2022, 14 different Hacker News readers have linked it 34 times, most often “For the Love of God, Stop Using CPU Limits on Kubernetes”. No feed was found, so read it on the site itself.
Too few sampled comments (7) to say how often HN recommends it.?
Why HN links it
Kubernetes blog whose 2022 post on stopping CPU limits is linked as the go-to case against them. Commenters also say the site is mostly content marketing, and one post on containers and chroot is called wrong.
Summarised by Claude from a sample of 7 HN comments that link here. Each comment is marked recommending, critical or neutral (citing without judging); how this works.
Robusta groups thousands of alerts into a handful of real incidents, investigates them with full context, and remembers every result.
Most-linked posts?
- For the Love of God, Stop Using CPU Limits on Kubernetes6 people · 7 mentions · first linked 2023-11-08
- For the love of god, stop using CPU limits on Kubernetes (updated)3 people · 4 mentions · first linked 2022-04-13
- Show HN: I wrote a profiler that combines dynamic profiling and static analysis2 people · 3 mentions · first linked 2022-02-24
- Kubernetes is a cloud operating system2 people · 2 mentions · first linked 2022-03-15
- Modern containers don't use chroot2 people · 2 mentions · first linked 2022-11-11
What Hacker News says?
Looks like a bad copy of: https://home.robusta.dev/blog/stop-using-cpu-limits "For the Love of God, Stop Using CPU Limits on Kubernetes" literally same title
Comment linking /blog/stop-using-cpu-limits
on “For the love of god stop using CPU limits in Kubernetes”Submitted For the love of god, stop using CPU limits on Kubernetes (updated) as a story · 47 points
HN discussionThis is the only thing you need to know: https://home.robusta.dev/assets/stop-using-cpu-limits-inline... The article behind it explains it better, but a quick glance at the image above is all you need if you don't care too much about the explanation. https://home.robusta.dev/blog/stop-using-cpu-limits
Comment linking /blog/stop-using-cpu-limits
on “For the love of god stop using CPU limits in Kubernetes”Submitted Kubernetes is a cloud operating system as a story · 29 points
HN discussionIf you want the slop-free inspiration (2022): https://home.robusta.dev/blog/stop-using-cpu-limits (The title of this was also stolen for this HN post, although the GitHub repo makes no mention of it...)
Comment linking /blog/stop-using-cpu-limits
on “For the love of god stop using CPU limits in Kubernetes”Submitted For the Love of God, Stop Using CPU Limits on Kubernetes as a story · 22 points
HN discussionOr just don't put CPU limits: https://home.robusta.dev/blog/stop-using-cpu-limits
Comment linking /blog/stop-using-cpu-limits
on “We should get rid of average CPU utilization”Submitted Kubernetes Is the New POSIX as a story · 16 points
HN discussionI found this article that sort of covers similar ideas really interesting too. https://home.robusta.dev/blog/stop-using-cpu-limits/
Comment linking /blog/stop-using-cpu-limits/
on “Kubernetes CPU allocation and throttling demystified”Submitted Show HN: I wrote a profiler that combines dynamic profiling and static analysis as a story · 10 points
HN discussionThe Kubernetes community has this discussion every other week. This article isn't wrong per-se (and it's mostly content marketing, they have articles that are just plain wrong too, like https://home.robusta.dev/blog/containers-dont-use-chroot - i caused the "updated" tag on that one), but it's sweeping in its assertions, ignoring many good reason to set limits. Workloads that use up all the bursting with little bene…
Comment linking /blog/containers-dont-use-chroot
on “Go, Containers, and the Linux Scheduler”Submitted You really shouldn't copy-paste errors into Claude Code as a story · 4 points
HN discussionThis sort of tuning isn't necessary if you use CPU reservations instead of limits, as you should: https://home.robusta.dev/blog/stop-using-cpu-limits CPU reservations are limits, just implicit ones and declared as guarantees. So let the Go runtime use all the CPUs available, and let the Linux scheduler throttle according to your declared reservations if the CPU is contended for.
Comment linking /blog/stop-using-cpu-limits
on “Go, Containers, and the Linux Scheduler”Submitted Robusta – an OSS platform for K8s monitoring, troubleshooting, and automation as a story · 3 points
HN discussionSubmitted For the love of god, stop using CPU limits on Kubernetes as a story · 3 points
HN discussionSubmitted For the love of god, stop using CPU limits on Kubernetes as a story · 2 points
HN discussionSubmitted When Is a CPU Not a CPU? Benchmark of Kubernetes Providers and Node Efficiency as a story · 2 points
HN discussionSubmitted The Importance of Empty States as a story · 2 points
HN discussionSubmitted Kubernetes is a cloud operating system as a story · 2 points
HN discussionSubmitted Combining CPU profiling and static analysis for better JupyterNotebook profiling as a story · 2 points
HN discussionSubmitted Kubernetes is complex because you want complex things as a story · 2 points
HN discussionSubmitted Kubernetes is complex because you like complex things as a story · 2 points
HN discussionSubmitted Show HN: Debug any Python application on Kubernetes in 60 seconds as a story · 2 points
HN discussionSubmitted How to Drive an LLM as a story · 1 points
HN discussionSubmitted Fairness, Kubernetes Pricing, and Burstable CPUs as a story · 1 points
HN discussionSubmitted Kubernetes Monitoring from Scratch as a story · 1 points
HN discussionSubmitted Hybrid profiling – combining static analysis and dynamic profiling as a story · 1 points
HN discussionSubmitted Modern containers don't use chroot as a story · 1 points
HN discussionSubmitted You can't have both high utilization and high reliability as a story · 1 points
HN discussionSubmitted For the love of god, stop using CPU limits on Kubernetes as a story · 1 points
HN discussion
