Peter Andreas Entschev

I forgot to mention, for UCX you should pass also `--ucx-net-devices auto` when running on a DGX-1. This will ensure each GPU utilizes the correct InfiniBand interface, which dramatically changes...

@charlesbluca as we discussed on our standup meeting last Friday, we also need to ensure UCX synchronizes on PTDS-only, rather than the default stream. Sorry for forgetting about this earlier,...

No, right now it will rely on your environment variables: https://github.com/pentschev/distributed/blob/c1cf54c6fc584efbc423ad0b49608817deb08d88/distributed/comm/ucx.py#L46-L49 We may change that in the future though.

As John mentioned, this is indeed a bug. Could you submit a PR for that when you have a chance?

> As in the above plots, mean and sum seem to have the most substantial performance boosts when using small chunks (in my case, 64) and large thread per worker...

Do any of the Jetson board have multiple GPUs @JasonAtNvidia ? Note that dask-cuda is targeting a one-process-per-GPU model for parallelism, and if none of the boards have multiple GPUs...

> There are Jetson boards with multiple GPU capability, DRIVE units are most common. They have a Xavier SoM and a Turing daughter board. Sorry for the late reply here...

@JasonAtNvidia I just pushed https://github.com/rapidsai/dask-cuda/pull/402 , this should work with Tegra, but I don't have access to a Tegra device to test, it would be great if you could test...

@JasonAtNvidia those are the correct functions. It would be interesting to know if you can go any further to do some Dask computation as well, but as I mentioned before,...

Thanks for the report @zbs , and @jrbourbeau for the ping. Disabling that is currently not possible without removing CuPy from your environment. Would removing CuPy be an alternative for...