Skip to content
This repository has been archived by the owner on Feb 22, 2022. It is now read-only.

[stable/dask] ability to set worker --nthreads and --nprocs independently of cpu resource limit #18708

Closed
skeller88 opened this issue Nov 8, 2019 · 4 comments
Labels
lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.

Comments

@skeller88
Copy link

A dask worker node should be able to have --nthreads and --nprocs set via a user-provided helm chart, and have those values be independent of worker cpu resources. One use case is high I/O workloads that benefit from more threads than cores.

Currently --nthreads is set to the worker cpu resource limit.

Aside from limiting dask helm deployment options, this limitation is problematic because it leads users to believe that there needs to be a 1-1 relationship between cpus and threads, which is not true.

A solution is to have a new option in the helm chart:

worker:
    args:
        nthreads: 6
        nprocs: 2

Other worker command line options could be added in this way.

@leoxtc
Copy link

leoxtc commented Nov 19, 2019

So currently I can not explicit set the nthreads from the helm chart config ?

@skeller88
Copy link
Author

skeller88 commented Nov 20, 2019 via email

@stale
Copy link

stale bot commented Dec 20, 2019

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Any further update will cause the issue/pull request to no longer be considered stale. Thank you for your contributions.

@stale stale bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Dec 20, 2019
@stale
Copy link

stale bot commented Jan 3, 2020

This issue is being automatically closed due to inactivity.

@stale stale bot closed this as completed Jan 3, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.
Projects
None yet
Development

No branches or pull requests

2 participants