store: Try to avoid pathological batch size adjustments#5792
Closed
store: Try to avoid pathological batch size adjustments#5792
Conversation
If a batch is processed very fast, that might indicate that there are very few rows actually matching the range. If this happens repeatedly, we can end up with a gigantic batch size where processing a batch takes way too long once we get into a region with denser vids. This patch tries to address that by taking a fast batch as an indication that vids are distributed sparsely and that we should jump directly to the next existing vid rather than adjusting the batch size.
Collaborator
Author
|
Closing this in favor of #5807 |
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
1 participant
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.
If a batch is processed very fast, that might indicate that there are very few rows actually matching the range. If this happens repeatedly, we can end up with a gigantic batch size where processing a batch takes way too long once we get into a region with denser vids.
This patch tries to address that by taking a fast batch as an indication that vids are distributed sparsely and that we should jump directly to the next existing vid rather than adjusting the batch size.