4 ms·
Even without the bug it will have negative effect on latency and generally is not really needed for un-metered workloads (there’re posts by thockin on reddit an
by dilyevsky 6y ago
Even without the bug it will have negative effect on latency and generally is not really needed for un-metered workloads (there’re posts by thockin on reddit and github that describe this in detail)
To answer your other question - I believe kops ships without system reserved by default
- rsanders 6y agoCan you explain how having a CPU limit set (at any level) has a negative effect on latency? That's an important factor to understand. The arguments for allowing containers to burst makes plenty of sense to me. I do it on most of my services! thockin's reddit post for reference: https://www.reddit.com/r/kubernetes/comments/all1vg/on_kubernetes_cpu_limits/efgyygu/?utm_source=reddit&utm_medium=web2x&context=3 https://www.reddit.com/r/kubernetes/comments/all1vg/on_kuber... Another interesting bit of context describing some of the non-intuitive impacts of CPU limits: https://github.com/kubernetes/kubernetes/issues/51135 https://github.com/kubernetes/kubernetes/issues/51135 Edit: added links
- dilyevsky 6y agoIt’s mentioned elsewhere on this thread but essentially with cfs quota period default which is 100ms it’s really easy for multithreaded process to exhaust the quota and just sit there idle until next period. Another thing is if you have spare cycles that you presumably already paid for why not just use them?