Artifact 5f3ffe2557c93eb7810422418677ca08c5e7483ec5427a51b3d60467a54e3d37:
- File
src/storage.zig
-
2026-08-07 13:03:45
— part of check-in
[f3becbedd1]
on branch sub-manifest
— storage: a block cache for FileStorage reads, opt-in and not yet wired
Profiling a real pkgsrc-scale import put readv at over half of all CPU samples. A block cache in front of pread is the shape that addresses it: the store is append-only, so a block is retained only when the read that filled it came back FULL -- which proves those bytes already existed, so appends cannot alter them and need no invalidation. Only truncate does.
Deliberately not attached to any caller. Wired into import-git it reached a 99 percent hit rate over 392,421 reads and did NOT make a small corpus faster: at that size the page cache already served those reads, so the syscalls were cheap and the lookup was pure overhead. The prior from the real profile is strong but unproven at scale, and shipping it on 'should help' is how the reverted top-level cache in issue 32 happened.
useReadCache is the one-line opt-in for profiling it. (#39) (user: dmestas, size: 19661) [annotate] [blame] [check-ins using]
- 2026-08-14 12:21:34 — part of check-in [8a45a021f9] on branch trunk — merge sub-manifest: delta-manifest dialect, R cards, diff hunks, server identity, stash, open/log resolution, clone remote+progress, timestamp names; e2e expectations updated (user: dmestas, size: 19661) [annotate] [blame] [check-ins using]
-
2026-08-07 13:03:45
— part of check-in
[f3becbedd1]
on branch sub-manifest
— storage: a block cache for FileStorage reads, opt-in and not yet wired