Add user option for column-major rank assignment. #85
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.
This PR introduces a new environment variable option,
CUDECOMP_USE_COL_MAJOR_RANK_ORDER, to enable users to change the default row-major rank assignment overpdimsto column-major.This can be useful when users have problems that require process grids like
2 x 8or4 x 8on a system with say, 4 NVLink connected GPUs per node (i.e. a small first dimension that is less than the number of NVLink connected GPUs). With the default row-major rank assignment, ranks are first assigned contiguously over the second dimension. This means that the first dimension, even though it is less than the number of NVLink connected GPUs, will span multiple nodes, resulting in slower internode communication for both the row and column communicators. Instead, if the rank assignment were column-major in this case, the ranks are first assigned across the small first dimension, resulting in a fast column communicator restricted to an NVLink connected group. This new option will enable users to realize this benefit in this type of situation.