-
Notifications
You must be signed in to change notification settings - Fork 63
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
Enable UCX protov2 in UCX >= 1.18.0 #1121
Comments
This was referenced Mar 13, 2025
rapids-bot bot
pushed a commit
that referenced
this issue
Mar 14, 2025
With protov1 not being actively developed anymore and protov2 now being more stable, it's time to switch permanently. See #1121 for more details. Closes #1121 . Authors: - Peter Andreas Entschev (https://github.com/pentschev) Approvers: - Mads R. B. Kristensen (https://github.com/madsbk) URL: #1122
rapids-bot bot
pushed a commit
to rapidsai/ucxx
that referenced
this issue
Mar 14, 2025
With protov1 not being actively developed anymore and protov2 now being more stable, it's time to switch permanently. See rapidsai/ucx-py#1121 for more details. Closes rapidsai/ucx-py#1121 . Authors: - Peter Andreas Entschev (https://github.com/pentschev) Approvers: - Mads R. B. Kristensen (https://github.com/madsbk) URL: #384
Changes are now merged and RAPIDS 25.06 (UCX-Py/UCXX 0.44) default to protov2, please let us know if you observe any negative impact because of that change. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
UCX has switched to protov2 in 1.16.0 (if I'm not mistaken), at the time there were some issues with it, like the lack of CUDA async memory support so we ended up hardcoding the choice for protov1 in both UCX-Py and UCXX. Now protov2 is more mature and should support CUDA async memory, plus newer architectures may not be at all supported in protov2, and protov1 is not actively developed anymore, so for RAPIDS 25.06 we plan to lift that hardcoded option but it may still be explicitly done setting
UCX_PROTO_ENABLE=n
.Should there be other issues with that change, please let us know here.
The text was updated successfully, but these errors were encountered: