Closes #5150: Try to fix bigint performance again #5151
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
1RyanK
force-pushed
the
5150-Try_to_fix_bigint_performance_again
branch
from
4203fbf to
17fc7be
Compare
1RyanK
requested review from
ajpotts,
drculhane,
e-kayrakli and
jaketrookman
1RyanK
force-pushed
the
5150-Try_to_fix_bigint_performance_again
branch
4 times, most recently
from
1ae145c to
8f7c20f
Compare
drculhane
reviewed
Dec 17, 2025
1RyanK
force-pushed
the
5150-Try_to_fix_bigint_performance_again
branch
from
295f9b6 to
b8a86e5
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
As seen in the issue, performance dropped again. Investigating what happened in this PR.
Check branch performance here and compare to main performance here.
Closes #5150: Try to fix bigint performance again