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
Selection of Network Ressources and creating worker/endpoint pair #9586
Comments
Currently, there is no API to select different resources per worker, but only per context. |
You may try to create 2 different context. It is an interesting discussion if this has to be supported per worker. |
Thank you for your response. I got now the functionality I want, with two seperate contexts. Each of them have one selectable network ressource. So far everything works and they do not interfer each other. I just read that it is suggested to only create one context. Which problems may occur if two contexts are created? |
Having two context is not a problem (this is how UCX was designed). With two workers under the same context so of the resource utilization (memory specifically) is more efficient when compared to two context. |
In my config I provide two selectable network ressources, which can be seen in the Context. Afterwards I create two worker / endpoint pairs but both select the same network ressources. Is there a way to force the second pair to use the other network ressource?
Setup and versions
The text was updated successfully, but these errors were encountered: