Kubernetes Throttling? It Doesn't Have to Suck!
We put a K8s cluster in the lab, overloaded it with CPU-hungry containers, and monitored what happened. Here's what we learned — and how you can fix throttling in your own clusters.
What You'll Learn
Kubernetes has a bad habit of throttling CPU resources — leading to degraded application performance or spiralling costs from over-provisioned infrastructure. In this session, we put a K8s cluster in the lab to monitor exactly how and when CPU throttling happens, then deliberately overloaded it with CPU-hungry containers to see how the cluster protects itself. You'll see real data showing how throttling impacts response times and learn practical techniques to detect, diagnose, and resolve it. We demonstrate how monitoring CPU throttling with Netdata helped reduce API response times by 7x and cut infrastructure resource requirements by 60–75%.
Key Takeaways
Your Host
Watch the Full Recording
Enter your details to instantly access the 45 minutes webinar recording.
Something went wrong. Please try again.
Enjoy the recording. Try Netdata free to see it in action.
No spam. Unsubscribe anytime.