From 33385f9572303e79bfb3811cc92cc8dd65e22261 Mon Sep 17 00:00:00 2001 From: Mario Zechner Date: Wed, 28 Oct 2026 18:53:50 +0000 Subject: [PATCH] docs(chord): attribution of the StoreStorage.close rule --- packages/chord/docs/next/decisions.md | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/packages/chord/docs/next/decisions.md b/packages/chord/docs/next/decisions.md index 7e7a96838..7c7b30647 100644 --- a/packages/chord/docs/next/decisions.md +++ b/packages/chord/docs/next/decisions.md @@ -1783,8 +1783,9 @@ validation and copies the v2 kernel added around Delta. - **Slice 6b: two numbers accepted (owner, 2026-10-27: "yeah the reopen times are ok"):** reopening a store with `StoreStorage` costs about 0.15 ms more than `SqliteStorage` once per open (0.28 to 0.43 ms: six table declarations, the allocator read, compiling the reads); the one-entry commit's mean is raised by one outlier among 20 samples while - its p75 is equal or lower. Neither is a hot path or a steady regression. `StoreStorage.close` waits for its commits - only (its reads go straight to the store, which stays open). + its p75 is equal or lower. Neither is a hot path or a steady regression. Accepted by the redesign session in fix + round 1 and shown to the owner (not his quote): `StoreStorage.close` waits for its commits only (its reads go straight + to the store, which stays open). - **The performance and memory bar, and converging reviews (owner, 2026-10-27: "yes"):** supersedes "as good as HEAD in everything" for Chord v2 slices and pi changes. CPU: each hot path (calls, changes, watches, links) within about 5% of HEAD, measured in bursts with alternating processes pinned to one CPU; worse is fixed or goes to the