Repository navigation
bench: carry actual file-owner state across A/B/A requests - #94
Draft
gspark-etri wants to merge 5 commits into
Draft
gspark-etri wants to merge 5 commits into
gspark-etri wants to merge 5 commits into
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.
A one-step benchmark with a restored donor hides the cost of returning to a consumed artifact. This Linux CPU benchmark carries the real Materializer's files, leases and naturally populated cache through initial A, requested B and requested A. P reconstructs without a donor; C copies from an intact donor through an explicit claim refusal; R delegates the real owner claim. P/C receive credit for retaining A and returning without another Pull, while every path still synchronizes and checks complete target SHA.
The caller records request-relative release, idle wait, construction, sync, full verification and lease boundaries, actual Pull/claim counters, file identities and phase occupancy. Existing roots and invalid origins are refused without modifying their contents. Model invocations require exact config and binary pins; failure preserves the attempt and stops the sequence.
Validation: CI41521328798 passed for source099c85f9 / tested merge5aeb2306: gofmt, vet, all Go race tests including actual A/B/A filesystem contracts, 77 Linux Python checks with no skips, retained timing replay, and both S3 conformance/CLI round trips. Expected implementation-RED and origin-mutation regression-RED runs were observed before their fixes. Independent connected-source recheck found no remaining Important issue.
This is the retention-allowed file regime, with declared allowances and phase snapshots rather than enforced quotas or measured peaks. Model cohorts remain not_run; constrained capacity, recovery, physical I/O and native service readiness remain separate experiments. Draft, stacked on PR92/e1b29c7, refs #93. No remote Job or device allocation is launched by this PR.