-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Improve substr() performance by avoiding using owned string #13688
Conversation
CI failure should be caused by #13686 |
I wonder if we can see perf change on TPC-H query 22 (which includes some substring expressions). |
538b44d
to
2cdba13
Compare
it seems |
I think merging the main branch can fix it. |
2cdba13
to
652b34c
Compare
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.
LGTM, thanks @richox .
TPC-H query 22 uses string_view_substr, seems not affected by this PR. cc @Dandandan
Ah makes sense |
Thanks @richox @jonahgao and @Dandandan |
…3688) Co-authored-by: zhangli20 <[email protected]>
…3688) Co-authored-by: zhangli20 <[email protected]>
Which issue does this PR close?
Closes #13687 .
Rationale for this change
What changes are included in this PR?
Are these changes tested?
tested with: cargo bench --bench substr
the result shows that
substr_string
andsubstr_large_string
are running much faster in all cases.Are there any user-facing changes?
no.