tweak: Update current validator stake mapping query #80
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
…query plan (used during stake/unstake finalization)
|
Kudos, SonarCloud Quality Gate passed! |
krzlabrdx
approved these changes
Apr 14, 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.
Update current validator stake mapping query to have a better query plan.
This query is used during stake/unstake finalization to create an estimated XRD-worth of the stake units - for the receipt which is stored in the pending transaction.
I've changed the query from an EF-Core query (which I believe suffers from this issue) to the manual query that's already been tuned to be very performant for the validators endpoint.
I'm talking to Theo to test that this change is (a) functional, and (b) more performant.