Verify forwarded reads after owner loss - #26
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.
Summary
Follow-up to merged PR #24. Add two regression checks for the metadata-free forwarded route:
Local verification
OutcomeUnknown(Fenced)and the authority root stayed at sequence zero. This PR does not change that existing contract or assertion.Temporary benchmarks and raw logs are outside the repository. The initial
join_allconcurrency comparison was biased because the zero-delay baseline could finish one request before polling the next; its reported 1.1 ms versus 2.8 ms p95 cannot establish a concurrency regression. A corrected release-build harness synchronizes 16 independently scheduled callers to one arrival timestamp.With a synthetic 2 ms object-read delay, the corrected full signed loopback peer + SQLite path reduced p95 from approximately 39 ms to 9 ms and lane completion time from 443–537 ms to 97–115 ms for 256 queries. Sender metadata body reads fell from three per query to zero. With zero delay, full-path results overlap and vary across pairs on the shared workstation; there is no demonstrated consistent latency or throughput gain in that condition. Production HTTP/provider p95 and sustained fleet throughput remain unmeasured.