[CELEBORN-2243] During the close phase of hashWriter, pushData and mergeData are sent in parallel #3574
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.
What changes were proposed in this pull request?
Optimize the close process of HashBasedShuffleWriter:
BeforePR:First, synchronously wait for pushData in the dataPusher queue to complete, then send mergeData and synchronously wait.
AfterPR:During the process of sending pushData by dataPusher, mergeData is also constructed and sent simultaneously.
Optimization results: The table below shows the shuffle write time for TPCH 1TB.
Note: This is the result of multiple optimizations combined;
other optimizations will be submitted as pull requests in the future.
Why are the changes needed?
Improve performance by increasing the parallelism of pushing/merging data.
Does this PR resolve a correctness bug?
NO
Does this PR introduce any user-facing change?
NO
How was this patch tested?
Exists Unit Test.