Improve performance for hash partition operator - #23507
Draft
tgujar wants to merge 14 commits into
Draft
Conversation
…ition-improvements
Contributor
Author
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.



Description
This change adds a staged scatter path for fixed-width hash partitioning. It computes compact row metadata once, then copies fixed-width output columns directly in partition order instead of materializing the whole result through a gather map. Variable-width columns and validity masks continue to use the existing gather machinery.
The implementation includes these optimizations:
bit widths allow it, with the existing representation retained as a fallback;
partition-total storage;
including vectorized 16-byte copies;
reduce scattered output sector writes;
all remaining materialization work.
Checklist