Add process binding arguments to horovodrun #1767
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
To maintain compute/memory locality, it is often good practise to
bind processes to NUMA nodes.
In ppc64le architecture with large models, I see a 20% performance gain
because tensor swapping happens between GPU memory and system memory and
CPU/GPU link (NVLINK) is faster than inter-socket link.
The PR also makes socket binding the default for SMPI (ppc64le). Even
with those flags, you may end up in a situation when a process with a GPU is bound to a
non-local CPU socket. That happens usually when GPUs are not split evenly across sockets or
you don't use all the GPUs of a node. In those cases, it
is recommended to use a rankfile to get more control: --binding-args="--rankfile myrankfile"
Signed-off-by: Nicolas V Castet nvcastet@us.ibm.com