Claude d567aec6de perf(geode): stream haveIds in the mirror up-catch-up instead of materializing ...

runCatchUpUp used negentropyReconcileIds, which builds the FULL need+have
id lists in memory even though the up direction only needs haveIds — on a
large window (e.g. 1M local events against an empty upstream) that is a
~100 MB+ heap spike per convergence round, plus a needIds list built and
immediately discarded.

Switch to the streaming negentropyReconcile: publish each haveIds batch as
it arrives (bounded to one batch of ids) and drop the need direction via a
no-op onNeedIds. The publish still suspends the reconcile round, so the
back-pressure and the reconcile-as-delivery-check convergence loop are
unchanged — only the peak memory drops from O(window) to O(batch).

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_012EZeWww5TJnzBZKPoc6mvU

2026-07-05 04:55:36 +00:00

..

plans

docs(geode): SQLite knobs A/B verdict — no winner, knobs stay off by default

2026-07-04 00:50:37 +00:00

src

perf(geode): stream haveIds in the mirror up-catch-up instead of materializing

2026-07-05 04:55:36 +00:00

build.gradle.kts

test(geode): sync-benchmark knobs + corpus-server tool for the negentropy comparison

2026-07-05 02:29:58 +00:00

config.example.toml

fix(geode): validate config knobs and mirror filter at boot

2026-07-04 02:32:35 +00:00