| Comment: | landing: correct the cost note, and stop naming a particular forge
The module doc claimed stores of this size read in milliseconds. They do not -- a 117MB mirror scanned for 62 seconds. The claim was carried over from a WRITE path taken once per ticket change onto a READ path taken per view, where neither the frequency nor the scale held. Removed rather than softened, with what the scan actually costs written down: still linear in store bytes, which the constant-factor fix did not change. The doc also named quarry throughout. zit provides the hooks; what is built on them is not zit's business, and naming one forge in the code reads as though it were. |
|---|---|
| Timelines: | family | ancestors | descendants | both | landing-doc |
| Files: | files | file ages | folders |
| SHA3-256: |
78d56a2177914994d1e32a51dbe77292 |
| User & Date: | dmestas on 2026-08-23 23:25:14.572 |
| Other Links: | branch diff | manifest | tags |
|
2026-08-23
| ||
| 23:32 | merge landing-doc: correct the cost note, drop the forge name check-in: 95ea2cb6b1 user: dmestas tags: trunk | |
| 23:25 |
landing: correct the cost note, and stop naming a particular forge
The module doc claimed stores of this size read in milliseconds. They do not -- a 117MB mirror scanned for 62 seconds. The claim was carried over from a WRITE path taken once per ticket change onto a READ path taken per view, where neither the frequency nor the scale held. Removed rather than softened, with what the scan actually costs written down: still linear in store bytes, which the constant-factor fix did not change. The doc also named quarry throughout. zit provides the hooks; what is built on them is not zit's business, and naming one forge in the code reads as though it were. closed check-in: 78d56a2177 user: dmestas tags: landing-doc | |
| 22:46 | merge landing-scan: the fold stops parsing every blob check-in: 0ef543c27a user: dmestas tags: trunk | |