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
We would like to use historical resource utilization data to predict future usage, and assign container memory and CPU requests within Kubernetes -- to optimize utilization.
To ensure we don't have negative impacts on the CI, we are starting with requests.
Because we are simply creating resource requests, it will still be possible for jobs to use more CPU/RAM than we expect. The next phase of experimentation will focus on instituting limits.
The ability to predict usage and assign requests has been implemented in the gantry web api, but there are a few steps needed to complete this goal.
We would like to use historical resource utilization data to predict future usage, and assign container memory and CPU requests within Kubernetes -- to optimize utilization.
To ensure we don't have negative impacts on the CI, we are starting with requests.
Because we are simply creating resource requests, it will still be possible for jobs to use more CPU/RAM than we expect. The next phase of experimentation will focus on instituting limits.
The ability to predict usage and assign requests has been implemented in the gantry web api, but there are a few steps needed to complete this goal.
The text was updated successfully, but these errors were encountered: