Documentation
¶
Overview ¶
Command soak asks one long-lived server the same questions over and over and checks that the answers do not drift.
It exists because a defect was found where results depend on process state rather than on the index: the same MATCH returned 489 rows from a clean process and 240 from one with the ONNX runtime loaded, and some queries failed outright with "database disk image is malformed" on a database that passes integrity_check. Whatever the mechanism, the observable is a served answer that changes without the index changing — which no correctness suite looks for, because they all ask each question once.
So this asks each question many times in ONE server, the way an agent session does, and reports the first round where an answer stops matching round 1.
Usage:
soak -bin dist/contextmaxxer.exe -index path/to/index.db [-rounds 20] [-queries file]