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
The Kubernetes way of doing things is to give a bit of slack to processes and set limits that are greater than the requests, to avoid killing jobs unnecessarily, while making efficient use of resources, by allowing a slight overcommit. We should maybe do that when we issue jobs.
Also, I have a run I want to resume where my memory limits are too low and the only way I can get my jobs to run is if Kubernetes gives them a bit more memory.
┆Issue is synchronized with this Jira Task
┆Issue Number: TOIL-459
The text was updated successfully, but these errors were encountered:
The Kubernetes way of doing things is to give a bit of slack to processes and set limits that are greater than the requests, to avoid killing jobs unnecessarily, while making efficient use of resources, by allowing a slight overcommit. We should maybe do that when we issue jobs.
Also, I have a run I want to resume where my memory limits are too low and the only way I can get my jobs to run is if Kubernetes gives them a bit more memory.
┆Issue is synchronized with this Jira Task
┆Issue Number: TOIL-459
The text was updated successfully, but these errors were encountered: