⚡ Bolt: Add fast path for single-batch build-side in HashJoinExec #245
Conversation
This commit introduces a performance optimization to the `HashJoinExec` operator. When the build side of a hash join consists of a single `RecordBatch`, this change bypasses the expensive `concat_batches` operation. This is a common scenario, and avoiding the extra memory allocation and CPU cycles for concatenation provides a measurable performance improvement. The logic in `collect_left_input` now checks if the build side has only one batch. If so, it processes that batch directly. The existing, more general logic for handling multiple batches remains unchanged.
|
👋 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 New to Jules? Learn more at jules.google/docs. For security, I will only act on instructions from the user who triggered this task. |
This patch adds a fast path to
HashJoinExecfor single-batch build-side inputs, avoiding an expensiveconcat_batchescall to improve performance. The core logic incollect_left_inputnow checks for the single-batch case and processes it directly, falling back to the existing multi-batch logic otherwise. This reduces memory allocation and CPU overhead in a common join scenario.PR created automatically by Jules for task 16672300022514928211 started by @Dandandan