[DOC] dask-cuda-worker with --ucx-net-devices="auto" errors
See original GitHub issueAfter installing the latest rapidsai 0.14 conda nightly packages, following the ucx-py blog post’s dask-cuda-worker startup instructions:
dask-cuda-worker ucx://10.10.10.10:8786 --enable-tcp-over-ucx --enable-nvlink --enable-infiniband --ucx-net-devices="auto"
results in an error about the ucx-net-devices
param:
Usage: dask-cuda-worker [OPTIONS] [SCHEDULER] [PRELOAD_ARGV]...
Error: no such option: --ucx-net-devices=auto
Issue Analytics
- State:
- Created 3 years ago
- Comments:7 (5 by maintainers)
Top Results From Across the Web
PTDS Benchmarks · Issue #517 · rapidsai/dask-cuda - GitHub
Some questions: Would this benchmark be better suited as a reproducible script, a one-off notebook with some plots to reflect the results, or...
Read more >High-Performance Python Communication with UCX-Py
UCX/UCX-Py is an accelerated networking library designed for low-latency high-bandwidth transfers for both host and GPU device memory ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Yes, I’m sorry, I thought we were talking about renaming to
--ucx-net-devices
in dask-cuda, which is something Ben and I discussed in the past. I have now fixed the blog, thanks @randerzander for bringing this up to our attention.I’ll leave this issue open as we intend to rename that to
--ucx-net-devices
in the future anyway.This is not relevant anymore since adding support for UCX >= 1.11.1, when we removed
--ucx-net-devices
. Closing.