[VL] Reuse byte[] buffers in shuffle read and broadcast serialization paths#11777
Merged
zhztheplayer merged 1 commit intoapache:mainfrom Mar 20, 2026
Merged
[VL] Reuse byte[] buffers in shuffle read and broadcast serialization paths#11777zhztheplayer merged 1 commit intoapache:mainfrom
zhztheplayer merged 1 commit intoapache:mainfrom
Conversation
Contributor
Author
|
@zhztheplayer can you please review this change? Thanks! |
zhztheplayer
approved these changes
Mar 20, 2026
Member
zhztheplayer
left a comment
zhztheplayer
left a comment
There was a problem hiding this comment.
Thanks. Do you have any benchmark number to share here?
zhztheplayer
changed the title
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
2 participants
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.
What changes are proposed in this pull request?
This PR makes changes to reuse temporary byte[] buffers instead of allocating new ones on every call.
How was this patch tested?
Existing UTs
Was this patch authored or co-authored using generative AI tooling?
No