Artifact b9182ccceba91b653e7ce777cc3b4a9b2b7b453fe24fa8711f69648694b70ecf:
- File
src/cmd/history.zig
-
2026-08-16 17:28:25
— part of check-in
[4b2fceeacd]
on branch frames-parallel
— frames verifies a batch across workers (#84)
Profiling the post-memo stream put 59% in artifact.verify and 38% in reconstruction, so the parallel target is verification, not reconstruction: reconstruction is what the plaintext memo made sequential-friendly, and fanning it out would contend on that cache.
Reconstruction stays single-threaded; a bounded batch is hashed by workers walking disjoint strides, then emitted in order. Workers touch no store, no cache and no allocator, so there is no queue, lock or atomic — join supplies the ordering. libfossil 2.35s -> 1.37s wall, byte-identical output. (user: dmestas, size: 102853) [annotate] [blame] [check-ins using]
- 2026-08-16 17:33:59 — part of check-in [c36e9952c2] on branch trunk — merge frames-parallel: verify a batch across workers (#84) (user: dmestas, size: 102853) [annotate] [blame] [check-ins using]
-
2026-08-16 17:28:25
— part of check-in
[4b2fceeacd]
on branch frames-parallel
— frames verifies a batch across workers (#84)