Fixes performance issue with HighestSequenceNrSql query #5420
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
lucavice
deleted the
5419-performance_fix_to_highest_sequence_nr_query
branch
Merged
|
@Aaronontheweb we finally rolled out the updated version to our production environment, and I just wanted to share how big of a difference this made to our DTU usage in Azure SQL during Akka bootup: Before (capped at 100% for almost 10 minutes): After (peaked at 8% for less than a minute): |
|
@lucavice what a tremendous improvement! Thank you for your contribution! |
|
Adding an issue to help us screen for this in the future: #5503 |
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.
Description of the PR purpose is provided in Issue #5419