perf(ltx): reduce root publication metadata - #55
Merged
Merged
Conversation
forhappy
marked this pull request as ready for review
October 4, 2026 11:46
Track the last physical reader when eligibility expands so a shorter candidate list cannot bias subsequent ties. Keep the original retry cursor and admission-aware load accounting. Wait for durability-test response telemetry explicitly before checking its exact object-source counts, since reply delivery wakes the waiter first. Preserve later log-backed execution and all qualification assertions.
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.
Prepare the final publication root directly from verified compaction state and embed a bounded descriptor tail to reduce metadata operations. Preserve fencing, the original authority predecessor, required lineage retention, origin checks, dependency barriers and cancellation cleanup.
Keep replica tie rotation anchored to the last physical reader as discovery changes eligibility. Synchronize the durability test with response telemetry before inspecting its exact source counts.
Update readers and writers of the current development-v1 root schema together. Earlier development roots require recreation under the existing format policy.
Validation: deterministic regressions, workspace/MSRV CI, object/follower qualification, constrained Compose smoke/scaling and application scenarios pass. The remaining routing comparison jobs are running. Descriptor-boundary, origin, upload-barrier and cancellation coverage remains in place.
Critical metrics, compared revisions, verification and limitations are tracked in the performance folder.