Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Control memory and CPU usage of containers during local training & packaging #641

Open
BPylypenko opened this issue Dec 16, 2021 · 0 comments
Open

Control memory and CPU usage of containers during local training & packaging #641

BPylypenko opened this issue Dec 16, 2021 · 0 comments
Labels
feature [Added] for new features. WG:local

Comments

@BPylypenko
Copy link
Contributor

BPylypenko commented Dec 16, 2021 •
edited
Loading

Is your feature request related to a problem? Please describe.
Sometimes, especially, when several containers are running simultaneously some of them are killed because of getting "out of memory" (137 docker error code).

Describe the solution you'd like
If the resource requests and limits are specified, then the containers have to adhere to them.
And should be some default values for resource limits & requests which should be specified in the documentation.

Possibly useful links:
https://docs.docker.com/config/containers/resource_constraints/
@BPylypenko BPylypenko added feature [Added] for new features. WG:local labels Dec 16, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
feature [Added] for new features. WG:local
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@BPylypenko