Files
codebase-memory-mcp/tests
Martin Vogel 35154ab9f2 fix(pipeline): spill before resolve when the strict resolver would pass the budget
The projection that decides whether results spill was fitted before the strict resolver, at 160 bytes per reference. Resolve now grows by up to 3,250 bytes per reference, so elasticsearch projected 2,534 MB against 26,479 MB real, kept its results in memory, and reached 29,755 MB charged against a budget of 22,488 MB. No phase after extraction can spill.

The refit is 3,400 bytes per reference, fitted to Java, the most expensive language measured. Elasticsearch now spills by itself and peaks at 16,833 MB charged, with no slowdown and all 12 graph fingerprints the same as in memory. Spilling changes when results park, not what is resolved, so this is no work cap. It over-reads other languages, which only costs disk reads: kubernetes projects 18,479 MB for 8,384 MB real, and still keeps results in memory at the full budget.

Nothing updates the constant. A later change that costs more per reference has to refit it.

Signed-off-by: Martin Vogel <martin.vogel.tech@gmail.com>
2026-11-02 22:04:47 +01:00
..
…