perf(arrow/csv): avoid materializing rows before writing - #1190
Draft
fallintoplace wants to merge 1 commit into
Draft
perf(arrow/csv): avoid materializing rows before writing#1190fallintoplace wants to merge 1 commit into
fallintoplace wants to merge 1 commit into
Conversation
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.
Rationale for this change
Writer.Writecurrently converts columns to strings, then copies every string header into a row-major[][]stringbefore callingWriteAll. This allocates one[]stringfor every row. Large record batches spend a lot of memory on this temporary matrix.What changes are included in this PR?
[]stringwhile writing each CSV record.For the existing 1,000-row, 16-column benchmark, medians from 6 runs on an Apple M1 Pro were:
This removes 999 allocations per call for 1,000-row batches.
Are these changes tested?
go test ./arrow/... -count=1go test ./arrow/csv -run "^$" -bench "^BenchmarkWrite$" -benchmem -count=6Are there any user-facing changes?
No. The generated CSV output is unchanged.