Skip to content

bench: carry actual file-owner state across A/B/A requests - #94

Draft
gspark-etri wants to merge 5 commits into
exp/88-timing-evidencefrom
exp/93-state-sequences
Draft

gspark-etri wants to merge 5 commits into
exp/88-timing-evidencefrom
exp/93-state-sequences

Conversation

@gspark-etri

@gspark-etri gspark-etri commented Nov 2, 2026 •

Copy link
Copy Markdown
Contributor

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant