Add batch coalescing in NetworkShuffleExec operations #242
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
CoalesceBatchesExecafter eachNetworkShuffleExecin order to sending bigger and fewer batches over the wire.While performing repartitions over the network, the same data stream might need be fanned out to a big number of output partitions, producing very small and numerous record batches, which can have a toll upon being sent as individual messages in the Arrow Flight stream.
With this change, record batches are coalesced into bigger ones so that less a bigger chunks are sent over the wire.
Benchmark results
This benchmarks were performed against a cluster of 4
t3.xlargemachines against TPCH stored in parquet files in S3 with a scale factor of 10npm run datafusion-bench -- --sf 10 --files-per-task 4 --shuffle-batch-size 0 # VS npm run datafusion-bench -- --sf 10 --files-per-task 4 --shuffle-batch-size 8192