Skip to content
Hallway
0:00 / 0:00

#netdata#cputhrottling#cgroups

Kubernetes throttling? It doesn't have to suck!

Netdata

1.9K subscribers • 1 video on Hallway

YouTube
  • Recommended by 1 person: 1 in engineering communities.
  • Made by the vendor. The company whose product it covers made or sponsored it.
  • An opinion. It argues one side of a question engineers disagree on.

Intermediate. Assumes working knowledge.

7.4K views4 years ago1 recommendation

Cloud and DevOpsSystems programmingKubernetesPerformance and optimizationObservability and monitoring

Netdata demonstrates the effects of CPU throttling on a Kubernetes cluster and shows how running without CPU limits affects stability.

Kubernetes has a bad habit of throttling CPU resources—leading to severely degraded performance or spiralling costs for extra, unnecessary infrastructure. We put a K8s cluster in the lab to monitor how and when CPU throttling happens. Then we tried to kill the cluster by overloading it with CPU-hungry containers. Watch this video to see how K8s clusters protect themselves from what they see as heavy CPU usage, and how you can monitor and troubleshoot the problem. We demonstrate how you can: – Use Netdata to reduce API response times by a factor of 7 – Expect to reduce infrastructure resource requirements by 60-75% Introduction To Throttle or Not to Throttle Kill the Cluster Takeaways Want to know more? Hit subscribe now to get the next installment of our series on Kubernetes monitoring and troubleshooting, then visit: Our website: netdata.cloud/integrations/kubernetes-monitoring/ Our documentation: learn.netdata.cloud/guides/monitor/kubernetes-k8s-netdata Thoughts, questions or suggestions? Share them on our Discord server: discord.gg/4ShKb65VvF Or on our community forum: community.netdata.cloud/

Why it's here

1 person recommends this

What people say. Recommended for its insights and experiments on running Kubernetes clusters without CPU limits.

u/ktsaouin r/kubernetes • Recommends

k8s without cpu limits? We put it on the lab to test it! Hi all, We have put a k8s cluster on the lab to understand CPU throttling and then we tried to challenge the cluster's stability when running without CPU limits, by starting about 500 CPU hungry containers on a cluster with just 20 cores. The results are amazing! Without limits the cluster is amazingly stable and reliable at high CPU load. This means CPU limits are not really needed and they should rarely be used, especially for web applications. We put this on production and we reduced web responses latency by a factor of 7. Check the whole test in this video: [video Comments are welcome...
53View on Reddit