-
Notifications
You must be signed in to change notification settings - Fork 3.6k
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
GH-41726: [C++][Parquet] Minor: moving EncodedStats by default rather than copying #41727
Conversation
|
cca042a
to
8faeb7a
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.
+1
It seems that we don't need to add "minor" in the PR title
@pitrou this is a short pr, would you mind take a fast glance? |
After merging your PR, Conbench analyzed the 7 benchmarking runs that have been run so far on merge-commit 8967ddc. There were no benchmark performance regressions. 🎉 The full Conbench report has more details. It also includes information about 10 possible false positives for unstable benchmarks that are known to sometimes produce them. |
…rather than copying (apache#41727) ### Rationale for this change Moving EncodedStats because it holds two std::string. This could benifit for non-SSO optimized data for FLBA/String statistics ( It seems to be useless for SSO optimized data?) ### What changes are included in this PR? 1. construct `EncodedStats` by `std::move` 2. Making uncompressing size checking ahead of compressing ### Are these changes tested? Covered by existing. ### Are there any user-facing changes? No * GitHub Issue: apache#41726 Authored-by: mwish <[email protected]> Signed-off-by: mwish <[email protected]>
Rationale for this change
Moving EncodedStats because it holds two std::string. This could benifit for non-SSO optimized data for FLBA/String statistics ( It seems to be useless for SSO optimized data?)
What changes are included in this PR?
EncodedStats
bystd::move
Are these changes tested?
Covered by existing.
Are there any user-facing changes?
No