Skip to content

⚡ Bolt: optimize single-batch build side in hash join#274

Open
Dandandan wants to merge 1 commit intomainfrom
bolt-optimize-single-batch-hash-join-4292392479032325427
Open

⚡ Bolt: optimize single-batch build side in hash join#274
Dandandan wants to merge 1 commit intomainfrom
bolt-optimize-single-batch-hash-join-4292392479032325427

Conversation

@Dandandan
Copy link
Copy Markdown
Owner

Implemented a fast path for single-batch build side in HashJoinExec to avoid redundant expression evaluations and concat_batches. This improves performance and efficiency for joins with small build sides.


PR created automatically by Jules for task 4292392479032325427 started by @Dandandan

This PR implements a performance optimization in `HashJoinExec` for the common case where the build side consists of a single `RecordBatch`.

💡 What:
- Added a fast path in `try_create_array_map` and `collect_left_input` for single-batch build-side inputs.
- Bypasses `concat_batches` and redundant `evaluate_expressions_to_arrays` calls.

🎯 Why:
- Previously, join expressions were evaluated on individual batches to build the hash map, then all batches were concatenated into one, and expressions were re-evaluated on the concatenated batch.
- For single batches, this resulted in exactly 2x the necessary CPU work for expression evaluation and an unnecessary data copy in `concat_batches`.

📊 Impact:
- Reduces CPU usage for the build phase of hash joins with small build sides.
- Improves memory efficiency by avoiding temporary allocations in `concat_batches`.

🔬 Measurement:
- Verified that all 355 join tests in `datafusion-physical-plan` pass.
- Logic follows existing deterministic LIFO insertion order for hash map collision chains.

Co-authored-by: Dandandan <163737+Dandandan@users.noreply.github.com>
@google-labs-jules
Copy link
Copy Markdown

👋 Jules, reporting for duty! I'm here to lend a hand with this pull request.

When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down.

I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job!

For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with @jules. You can find this option in the Pull Request section of your global Jules UI settings. You can always switch back!

New to Jules? Learn more at jules.google/docs.


For security, I will only act on instructions from the user who triggered this task.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant