⚡ Bolt: Optimize Hash Join for Single-Batch Build Side#254
⚡ Bolt: Optimize Hash Join for Single-Batch Build Side#254google-labs-jules[bot] wants to merge 1 commit intomainfrom
Conversation
Adds a fast path to the `collect_left_input` function to avoid the expensive `concat_batches` operation when the build side consists of a single `RecordBatch`. This optimization reduces memory allocation and CPU usage for this common scenario.
|
👋 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. |
collect_left_inputfunction in theHashJoinExecoperator. It avoids the expensiveconcat_batchesoperation when the build side of the join consists of a singleRecordBatch.concat_batchesfunction allocates new memory and copies data, which is unnecessary overhead when there's only one batch. This change improves performance for a common join scenario.PR created automatically by Jules for task 4148456866613629032 started by @Dandandan