You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When you have CPU requests, you are guaranteed to have those requests and the app works fine, but if there are no more resources than the app simply won't have them. If there is, then the app is going to use them for when it needs it, and it will perform better for that period and will return to its requested -- and, again, work fine -- in case someone else requests the available resources.
With CPU limits, the app won't take the additional resources when it needs them even though there are resources available, and that is a waste.
In short, for most of the time, the app will use its requested CPU and will just burst for a short period when it needs it, there is no point in preventing it from using it if is free and no one else has requested it.
The text was updated successfully, but these errors were encountered:
Look at this tweet by Tom Hockins, one of the original maintainers of Kubernetes: https://twitter.com/thockin/status/1134193838841401345
When you have CPU requests, you are guaranteed to have those requests and the app works fine, but if there are no more resources than the app simply won't have them. If there is, then the app is going to use them for when it needs it, and it will perform better for that period and will return to its requested -- and, again, work fine -- in case someone else requests the available resources.
With CPU limits, the app won't take the additional resources when it needs them even though there are resources available, and that is a waste.
In short, for most of the time, the app will use its requested CPU and will just burst for a short period when it needs it, there is no point in preventing it from using it if is free and no one else has requested it.
The text was updated successfully, but these errors were encountered: