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.

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

feature proposal: resource management on argo/kubeflow #68

Open
edublancas opened this issue Feb 10, 2022 · 0 comments
Open

feature proposal: resource management on argo/kubeflow #68

edublancas opened this issue Feb 10, 2022 · 0 comments

Comments

@edublancas
Copy link
Contributor

edublancas commented Feb 10, 2022

We want to add support for pipelines exported to argo and kubeflow to request specific resources for a given task (memory, CPU, GPU).

I'm thinking we could have a mapping in the config that matches task names to environments with certain characteristics:

my-config:
  resources_mapping:
    # train task should use this resources
    train:
      memory: some-value
      cpu: some-value
    # support for wildcards - all tasks with the fit- prefix should execute with this resources
    # say: fit-some-model, fit-some-other-model
    fit-*:
      memory: some-value
      cpu: some-value

I found this on argo's documentation, I think this is what we need.

Kubeflow uses argo under the hood, so I'm guessing it uses the same mechanism but if anyone has a link to the kubeflow docs that explain this part, please share it.

what it isn't clear to me is how the GPU comes into play here. Please comment if you have any extra info.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant