[SPARK-2650][SQL] Try to partially fix SPARK-2650 by adjusting initial buffer size and reducing memory allocation #1769
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.
JIRA issue: SPARK-2650
Please refer to comments of SPARK-2650 for some other details.
This PR adjusts the initial in-memory columnar buffer size to 1MB, same as the default value of Shark's
shark.column.partitionSize.mb
property when running in local mode. Will add Shark style partition size estimation in another PR.Also, before this PR,
NullableColumnBuilder
copies the whole buffer to add the null positions section, and thenCompressibleColumnBuilder
copies and compresses the buffer again, even if compression is disabled (PassThrough
compression scheme is used to disable compression). In this PR the first buffer copy is eliminated to reduce memory consumption.