Repository navigation
perf: Try to load previous seqNr if missing, in validation (backport 1.5) - #1229
Merged
Merged
Conversation
* perf: Try to load previous seqNr if missing, in validation * makes it more safe to evict from memory, but keep more in database * a step towards lazy loading of offsets, but full lazy loading would require many more changes due to the concurrency model used in the R2dbcOffsetStore * otherwise it will use timestampOf, which are be more costly for gRPC projections * it still falls back to timestampOf as last resort * different sql for SqlServer (cherry picked from commit e956248)
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
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.
Backport of #1197
perf: Try to load previous seqNr if missing, in validation
makes it more safe to evict from memory, but keep more in database
a step towards lazy loading of offsets, but full lazy loading would require many more changes due to the concurrency model used in the R2dbcOffsetStore
otherwise it will use timestampOf, which are be more costly for gRPC projections
it still falls back to timestampOf as last resort
different sql for SqlServer
(cherry picked from commit e956248)