This repository has been archived by the owner on Sep 18, 2023. It is now read-only.
[NSE-362] use arrow-unsafe allocator by default #363
Merged
Conversation
This file contains 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
This patch makes arrow-unsafe allocator as default profile arrow-netty will instance netty memory pool to reduce the alloc/dealloc overhead which introduced big memory footprint. local perf tests showed the performace is not heavily impacted after switch to arrow-unsafe one more benefit is we could remove the -XX:MaxDirectMemorySize flag which also impacts the vanilla Spark memory usage Signed-off-by: Yuan Zhou <[email protected]>
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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 were proposed in this pull request?
This patch makes arrow-unsafe allocator as default profile
arrow-netty will instance netty memory pool to reduce the
alloc/dealloc overhead which introduced big memory footprint.
local perf tests showed the performace is not heavily impacted
after switch to arrow-unsafe
one more benefit is we could remove the -XX:MaxDirectMemorySize flag
which also impacts the vanilla Spark memory usage
Signed-off-by: Yuan Zhou [email protected]
fixes #362
How was this patch tested?
locally verified