[Performance] Optimize the use of alternative streams in dataloader #4177
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.
Description
Main changes:
Before, only node/edge features transfer can overlap with the last step's computing kernels, while the subgraph transfer is not in the alternative stream. There is a launch gap between the H2D copy and the following computing kernels.
With this PR, all data transfer in the dataloader can overlap with computation, and the launch gap is reduced.
The timeline comes from RGCN training on MAG240M.
Checklist
Please feel free to remove inapplicable items for your PR.
or have been fixed to be compatible with this change