Repository navigation
perf(runtime): group queued mutations behind one durable root - #54
Merged
Merged
Conversation
forhappy
marked this pull request as ready for review
October 3, 2026 23:09
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.
Object-only writes previously captured and published a durable root for every command. Group up to four already-queued mutations per Cell into one transaction and publication, while preserving individual request identities, outcomes, and commit sequences. Successful replies still require the exact durable root covering each command; reads and other barriers retain FIFO ordering.
Release completed request slots before reply delivery to prevent immediate follow-up reads from receiving capacity refusals. Overlap independent LTX work and refill bounded compaction transfers as sources finish, preserving descriptor/error order, fencing, recovery checks, and resource limits. Update the routing test observer to validate grouped publication ranges.
Validation:
98ba666.Performance reports and versioned datasets, including regressions and measurement limitations, are tracked in the performance folder.