-
Notifications
You must be signed in to change notification settings - Fork 2.1k
perf: Add append_with to string builders, use in replace
#22029
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
neilconway
wants to merge
4
commits into
apache:main
Choose a base branch
from
neilconway:neilc/perf-builder-append-writer
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
+697
−51
Open
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
Oops, something went wrong.
Oops, something went wrong.
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.
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Wondering about the
from.is_empty()branch — the per-write trade-off looks unusually unfavorable here. Is it worth adding afrom_emptybenchmark case?There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
FYI, I ran the benchmarks locally for the empty_from cases and it does look like this branch causes a regression.
Uh oh!
There was an error while loading. Please reload this page.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Really interesting! Thanks for raising this.
I didn't quite follow your comment about the per-write tradeoff: I don't think there's anything fundamental about
append_withthat should be slower for the many-small-writes case (and we still are able to avoid a finalmemcpy). However, I can reproduce the significant slowdown you suggested for the "emptyfrom" case. I dug into why, and it seems that repeatedly extending an ArrowMutableBufferis relatively slow:StringWriter::write_str()doesMutableBuffer::extend_from_slice(&[byte]), which results in a libcmemcpyfor every call, which is obviously slower than per-charString::push(c), as the original code does. I don't thinkMutableBuffer::extend_from_slice(&[byte])is inherently slow, but there was enough helper functions / abstractions here that LLVM didn't inline, which lead to the per-callmemcpy.A few options:
replacewith empty-from is a corner-case. But it's unfortunate to leaveappend_withwith a performance footgun like this.mut Stringbuffer for the empty-from case. Fixes this specific workload but doesn't fix the underlyling issue inStringWriter.StringWriterfor small-string writes.I've implemented (3). A combination of special-casing the string length and marking functions as
#[inline(always)]appears to convince LLVM to vectorize this code path, which is a nice win (30-40% faster thanmainfor the empty-from). All the inlining might in theory cause code block for other callers but it doesn't appear to regress any otherreplacebenchmarks, at least.