manifest.zig keeps sealed-segment metadata resident, so the 39.5 GiB of oversized per-block blooms must be loaded before backfill can start. Measured startup latency (process start -> "starting repository backfill") across experiment 6: early in the run: 2.0 min median by hour 54: 4.5 min median (last 10 restarts) It doubled as the archive grew, which is what you would expect if the cost tracks resident bloom bytes rather than anything fixed. The process restarts about every 45 minutes at the batch boundary, so this is roughly 10% of wall-clock time in startup and climbing -- about 1.8h of the 17.6h of crawl still remaining. Same root cause as the memory ceiling already recorded here, so right-sizing the blooms should shrink the resident footprint and this recurring startup tax together. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>