Overview
| Comment: | Report the sync clone benchmark's server phase honestly: drop the unmeasurable walk+compress vs decode+parse split and show only the standalone compression micro as a share of respond, since scanRequest and emitCloneReply are private so parse and walk can't be told apart at the public boundary. |
|---|---|
| Timelines: | family | ancestors | descendants | both | bench |
| Files: | files | file ages | folders |
| SHA3-256: |
53962101c0d3961a493a1fc3c88dd262 |
| User & Date: | dmestas on 2026-07-16 02:35:11.048 |
| Other Links: | branch diff | manifest | tags |
Context
|
2026-07-16
| ||
| 02:41 | Land the out-of-band sync clone benchmark on trunk: it splits clone time into build/frame/decode/respond/reframe/consume/persist/reopen phases behind a convergence-verified in-process clone, and attributes per-artifact cfile compression as a faithful share of the server respond phase, so the first clone-speed optimization targets measured work rather than a guess. check-in: 5f6f1286d1 user: dmestas tags: trunk | |
| 02:35 | Report the sync clone benchmark's server phase honestly: drop the unmeasurable walk+compress vs decode+parse split and show only the standalone compression micro as a share of respond, since scanRequest and emitCloneReply are private so parse and walk can't be told apart at the public boundary. closed check-in: 53962101c0 user: dmestas tags: bench | |
| 02:10 | Split the sync benchmark's server phase into timed decode, respond and reframe steps plus a standalone cfile-compression measurement, so clone-speed work can tell inbound igot decode+parse apart from the actual per-artifact compression instead of trusting one opaque server label. check-in: 997edb13b5 user: dmestas tags: bench | |
Changes
Modified src/sync_benchmark.zig
from [c926f737a8]
to [2cb9f8b0a6].
[diff]