Skip to content
zit Check-in [645e0a6060]
Login

Check-in [645e0a6060]

Overview
Comment:A no-op sync or pull does work in proportion to what changed: nothing is persisted when nothing arrived, the store is opened once for its settings, resolved clusters and outstanding sub-manifest references are kept in sidecars checked against the log, and fork leaves come from the cached view, so a no-op sync at 42k files costs about 7 ms of CPU instead of 476
Timelines: family | ancestors | trunk
Files: files | file ages | folders
SHA3-256: 645e0a60605fefd144737fba166a30e849c89aa389cf0a1945da6fd478cf7b25
User & Date: dmestas on 2026-11-07 01:41:57.718
Other Links: manifest | tags
Context
2026-11-07
01:41
A no-op sync or pull does work in proportion to what changed: nothing is persisted when nothing arrived, the store is opened once for its settings, resolved clusters and outstanding sub-manifest references are kept in sidecars checked against the log, and fork leaves come from the cached view, so a no-op sync at 42k files costs about 7 ms of CPU instead of 476 leaf check-in: 645e0a6060 user: dmestas tags: trunk
01:21
A process reads and checks its .zit-checkout container once and serves every section from those bytes, and annotate opens the repository the fast way, so info, cat and annotate cost about a millisecond less at 42k files check-in: 0856fc67a4 user: dmestas tags: trunk
Changes