-
Notifications
You must be signed in to change notification settings - Fork 875
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
Faster decimal parsing (30-60%) #3939
Merged
Merged
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
Dandandan
reviewed
Mar 25, 2023
Dandandan
approved these changes
Mar 25, 2023
tustvold
reviewed
Mar 25, 2023
tustvold
reviewed
Mar 25, 2023
Co-authored-by: Raphael Taylor-Davies <1781103+tustvold@users.noreply.github.com>
I added some failing tests for "+", "-" and "". However, any attempt of fixing this (such as a simple "is_empty" check after handling the sign) has a big performance impact for up to up to 70%, that I cannot explain yet. |
Nice work 👍 |
tustvold
approved these changes
Mar 31, 2023
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.
Which issue does this PR close?
Rationale for this change
Improves decimal parsing performance. For me, this is now faster than attempting to split at the decimal point and
using
lexical
for the whole and fraction (of course that might also be how I implemented it).For
Decimal128
:For
Decimal256
:What changes are included in this PR?
The decimal precision that is supported by arrow ensures that there cannot be any overflows.
Are there any user-facing changes?