Closed
Conversation
Replace sequential send loops in wait_for_task with futures::future::join_all to send to all output partitions concurrently instead of one at a time. https://claude.ai/code/session_01GDTBavJzih6tSSBd9SRNmk
Contributor
Author
|
run benchmarks |
|
🤖 |
|
🤖: Benchmark completed Details
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Which issue does this PR close?
Rationale for this change
The current implementation sends error messages to output partitions sequentially using a for loop. This can be inefficient when there are many output partitions, as each
send()operation is awaited individually. By usingfutures::future::join_all(), we can parallelize these operations, allowing multiple sends to happen concurrently rather than sequentially.This change improves performance in error scenarios by reducing the total time spent notifying all output partitions of errors or completion.
What changes are included in this PR?
Are these changes tested?
The changes are covered by existing tests in the DataFusion test suite. The refactoring maintains the same functional behavior (all error messages and completion signals are still sent to all output partitions), only changing the execution model from sequential to concurrent.
Are there any user-facing changes?
No user-facing changes. This is an internal optimization to the physical execution layer that improves performance without changing the external API or behavior.
https://claude.ai/code/session_01GDTBavJzih6tSSBd9SRNmk