Repository navigation
Fix cold quota retry starvation - #15
Merged
Merged
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
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.
Under cold-store pressure, an oversized oldest buffer could be retried after every unrelated queue submission, repeatedly preventing a smaller buffer from being evicted. Keep its quota refusal valid until an accepted write can change that child or cold-store space changes. Unknown accepted access conservatively permits retries.
Retains oldest-first selection, busy-buffer guards, and cold quota accounting. A device latch avoids extra submit parsing in sync-only mode before the first quota refusal.
Validation: a deterministic CPU regression fails before the fix and passes afterward, including a real 1 MiB quota refusal and successful 256 KiB snapshot. Normal and hook-enabled bootstrap checks cover reads, empty submissions, scoped writes, unknown access, quota changes, and epoch saturation. Full CPU suite and production build results are recorded in validation/reactivity-2026-10-19. No game performance claim.