Container CPU Usage and Throttling

6th chunk of `content/en/blog/_posts/2016-11-00-Kubernetes-Containers-Logging-Monitoring-With-Sematext.md`

631709900dcd6e2210250052aa3b6e4f0bf5a89fec19e00700000001000002d3

![](https://lh6.googleusercontent.com/Qq1_FhJRC72H0fvc71Oy_RqxbmBe8IZ4L4JTtADxBfLAjopRv2tJW5Fvc8DstD6iOj9JKfNt8U2gWAxzedx9tdnHuld-k1agDMAXDyWM-AuLOs7IDi-KNxEj_p-Kwef12SjeAiVc) |
| Container memory usage, limits and fail counters |


Container CPU usage and throttled CPU time. The CPU usage can be limited by CPU shares - unlike memory, CPU usage it is not a hard limit. Containers might use more CPU as long the resource is available, but in situations where other containers need the CPU limits apply and the CPU gets throttled to the limit.



 ![](https://lh5.googleusercontent.com/iSMZcZROnz6jovMg9XVlHSYFSiOgpgbrcJ0dVK7aXRaXq0psyAHE_Y4mN3aD0k2yRjH-Lgr-X3prNtBexFNmaNdWNXFd0MNnDSwjo8hbgNXydgRWjaT1X-_xbD6f_U92z9VMf4C7)

Title: Container CPU Usage and Throttling

Summary

This section describes monitoring container CPU usage and throttled CPU time. CPU usage can be limited by CPU shares, but unlike memory, this isn't a hard limit. Containers can use more CPU if available, but when other containers need resources, CPU throttling occurs. The provided image visualizes container CPU usage.