From e02a7c89b41192ee1b424cda4161c25895c97410 Mon Sep 17 00:00:00 2001 From: Daan Meijer Date: Tue, 3 Nov 2026 19:52:52 +0100 Subject: [PATCH] REBUILD.md: probe_candidates back on the NVMe (migration 7300) Co-Authored-By: Claude Fable 5.1 --- REBUILD.md | 11 +++++++---- 1 file changed, 7 insertions(+), 4 deletions(-) diff --git a/REBUILD.md b/REBUILD.md index 57afb44..4bc685e 100644 --- a/REBUILD.md +++ b/REBUILD.md @@ -717,10 +717,13 @@ releases; the inspector matches them again), `nntp_shares`, `nodes`, - Gone: `fragments`, `range_blocks`, `release_final()` (final = finished: `settled_at IS NOT NULL`), the settler, the fragment merger, `releases_category_newest_idx`. -- `release_inspections` and `probe_candidates` on `CHUNK_TABLESPACE` (the - HDD) with their indexes. Note LOG.md 2026-10-19 (81): the judge's fake - rule read all of `release_inspections` every round, 17 min on the HDD; - the judge must read it by release or keep what it needs on the NVMe. +- `release_inspections` and `probe_candidates` were on `CHUNK_TABLESPACE` + (the HDD) with their indexes; both are back on the NVMe (migrations 4800 + and 7300). Note LOG.md 2026-10-19 (81): the judge's fake rule read all of + `release_inspections` every round, 17 min on the HDD; and 2026-11-03 + (136): the prober's catalog claim updates `probe_candidates` from random + points every minute, 2–3 min on the HDD beside the pending ladder's sweep. + What a worker reads or updates by random key every minute stays on the NVMe. ### Batch store (built 2026-10-25)