Overview
| Comment: | Use the known reconstructed size for a delta corpus artifact's USIZE instead of re-parsing the delta header: the bench just created the delta from cur, so its reconstructed target is cur and its length is the section 7.2 USIZE directly, dropping a redundant header parse. |
|---|---|
| Timelines: | family | ancestors | descendants | both | delta |
| Files: | files | file ages | folders |
| SHA3-256: |
3bdb4f96c01ddec0c2fce4c41f9ab5e1 |
| User & Date: | dmestas on 2026-07-16 04:50:26.786 |
| Other Links: | branch diff | manifest | tags |
Context
|
2026-07-16
| ||
| 05:01 | Drop the unused putContainer store method and its two tests: its only intended caller is the deferred client-verbatim persist hook, so it stays dead surface until that lands. closed check-in: 673d5070bb user: dmestas tags: delta | |
| 04:50 | Use the known reconstructed size for a delta corpus artifact's USIZE instead of re-parsing the delta header: the bench just created the delta from cur, so its reconstructed target is cur and its length is the section 7.2 USIZE directly, dropping a redundant header parse. check-in: 3bdb4f96c0 user: dmestas tags: delta | |
| 04:47 | Delta-encode blobs and manifests on ingest and serve them verbatim as section 7.2 delta cfiles on clone: store a commit's blob (against the same path's parent blob) and manifest (against the primary parent) as a delta when it comes in materially smaller and within the write-depth cap, carry the reconstructed-target size from the delta header as the cfile USIZE rather than the container's raw-delta-length prefix, and retransmit the stored delta container byte-for-byte so a chained-corpus clone reply drops 58-87 percent while a full-form corpus is byte-identical to before. check-in: 71235bf3be user: dmestas tags: delta | |
Changes
Modified src/sync_benchmark.zig
from [9cf13b063c]
to [053c44e967].
[diff]