PGTransport: add inplace transport (3x faster) #119
Merged
+253
−81
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 adds a new
state_dict
argument toPGTransport
that when provided will give a state_dict to use for doing in-place tensor operations. This has been measured at ~3x faster.Test plan:
Correctness:
The improvements have been measured via
pg_transport_bench
.For inplace operation we see it at ~3x faster (15s -> 4-5s) for 12GB with 3MB tensors size. The remaining overhead is primarily from torchft ProcessGroupBaby queue communication and not proportional to the size of the tensors.
Reducing this overhead requires some careful consideration and will be addressed in a follow up PR.
inplace
12GB/3MB (4k tensors)
16KB/4B (4k tensors)
48GB/12MB (4k tensors)
not inplace
12GB/3MB (4k tensors)