mrmrs-10a6b5

Closed into main

2 commits · 3 files ~3 modified

Description

Add a controlled actual-Serve benchmark lane for the legacy selected-branch clone path. Pin fixture/server/client provenance; compare head, manifest, history, worktree bytes/modes, local artifacts, receipt and normalized network work; expose clone plus first status/no-op commit costs and stat-cache validity. Require explicit control identity and harness-controls markers, isolate credentials, bound processes, and state that A/A plus quiet-host evidence remain necessary before any timing claim.

Commits 2

Files 3

scripts

M task_loop.py

tests

M test_task_loop.py

M README.md

@@ -331,8 +331,40 @@

331331 --oak-local-bin /path/to/current-oak \

332332 --scenarios interrupted_publication_after_request_v1 \

333333 --runs 10 --randomize-subject-order

334+

335+# Legacy selected-branch clone materialization. Run separate A/A and A/B

336+# configs with the same immutable Serve binary and at least 10 randomized

337+# pairs. Its fixed fixture has 192 regular 16 KiB files (eight executable),

338+# one empty file, and one selected-branch-only file: 194 paths total. Fresh

339+# destinations do not imply cold OS cache.

340+OAK_BENCH_LOCK_PATH=/Users/mrmrs/o/oak-bench-measurement.lock \

341+python3 scripts/task_loop.py \

342+ --config /abs/path/subjects-ab.toml \

343+ --subjects oak_baseline,oak_candidate \

344+ --oak-serve-bin /abs/immutable/fixed-oak-serve \

345+ --oak-serve-source-head 64_HEX_HEAD \

346+ --materialization-baseline-subject oak_baseline \

347+ --scenarios legacy_selected_clone_materialization_v1 \

348+ --runs 10 --randomize-subject-order --random-seed 46802 \

349+ --materialization-timing-controls-met \

350+ --workdir /abs/worker-owned/materialization-ab/work \

351+ --results /abs/worker-owned/materialization-ab/results

334352 ```

335353

354+Add `--oak-serve-source /abs/read-only/exact-head-checkout` when that immutable

355+checkout is retained; otherwise rows explicitly record that only the supplied

356+source head and binary hash were available for provenance.

357+

358+The scenario records raw proxy byte/connection totals, but its correctness gate

359+uses normalized pull phases, response/object/chunk counters, and connection

360+count; it does not pretend variable HTTP framing is product work. Clone, first

361+post-clone status, and first no-op commit are separate rows. The harness marks

362+only that its local timing controls are met when

363+`--materialization-timing-controls-met` is explicit, the shared lock is held,

364+order is randomized, and at least ten runs are present. That marker is not a

365+standalone speedup claim: the documented quiet-host window and a separate

366+interleaved A/A noise campaign are still required evidence.

367+

336368 These cells are different evidence classes. Local Git wall time is not a

337369 network comparison, and the Oak local-server row is loopback-only. Its second

338370 checkout is fresh and does not claim shared-object or OS-cache warmth. The

@@ -344,6 +376,11 @@

344376 and stay explicit skips rather than synthetic passes. Use

345377 `parallel_contention.py --modes workspace_per_task` for concurrent isolated

346378 tasks instead of duplicating its worker implementation here.

379+The materialization cell is Oak-before versus Oak-after only. Its setup probe

380+must first observe the exact legacy two-pull/two-pass route; one fixed Serve

381+and one repo are then shared by all subjects. Receipt phases, proxy byte counts,

382+HEAD, history, file bytes, and modes are correctness gates. Establish the A/A

383+noise floor before interpreting A/B timing.

347384

348385 Mount and acquisition probes:

349386