Optimize Parquet file writing with WriteBatch function #1028
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
reuster986
approved these changes
Jan 18, 2022
ronawho
approved these changes
Jan 18, 2022
stress-tess
approved these changes
Jan 18, 2022
This was
linked to
issues
Jan 20, 2022
Closed
20 tasks
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.
This PR changes from using the simple
WriteTablefunction provided by the Parquet API to a lower-levelWriteBatchfunction that allows greater control of writes. This optimization to Parquet writing in Arkodua is very similar to the reading optimization from #1014.Performance numbers collected on chapcs:
So we are seeing about a 10x improvement for writing Parquet files on chapcs.