Repository navigation
bench: publish verified three-node store-versus-peer E11 results - #83
Merged
Merged
Conversation
gspark-etri
marked this pull request as ready for review
October 31, 2026 02:39
Contributor
Author
|
Final verification at head
Proceeding with the authorized GitHub-flow squash merge. |
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.
Closes #82.
Measure the existing file-only B4/S256→B4/S512 transition on three eligible 1GbE Kubernetes nodes without accelerator resources. Four cache/arm conditions each have five simultaneous three-node cohorts (20 main, 60 node samples); four smokes and both setup attempts are retained. All target full-file hashes pass, no main retries/exclusions, and all owned CPU Jobs/Pods and the dedicated namespace are removed by UID.
With one seed in both arms, origin pack payload drops 395,822→0 B. Metadata remains 69,693,294 B, so all successful origin response bodies drop only 0.564740%. Empty peer snapshots provide no peer payload. Observed cohort medians store→peer: empty 3.102→3.240 s; one-seed 3.296→3.014 s. Report includes IQR and per-node times; no general latency speedup claim. Origin colocation, static snapshots, uncontrolled OS/load, instrumented proxy and application-byte scope are explicit.
Raw: 128-file package, tag
ccgrid-e11-20261031-raw-v1; measured harness7870cef872e201a6a4dca87ed1bb998da9c3109f, runtime05c97605b07882f9ceaaeb90b94878f8923f81cf. Report, summary and PDF/SVG/PNG figure included.Validation: seven accounting/validity regressions; offline verifier reconstructs all cohort counters from 26,928 original request rows, checks controller copies, cache/variant and source identities, actual node assignment and UID cleanup. Independent evidence review and clean Git archive reproduction pass; corruption is rejected. CI now reproduces the committed summary in addition to Go vet/race/build and real S3 conformance/CLI suites. Model payloads are absent from Git; offline checks compare worker-recorded full hashes with frozen inventories. No runtime behavior changes; NUMBERS.md untouched.