Kaineros · measured

Benchmark

It answers in about a second and a half.

A small model reading a compiled, on-device memory — where feeding a much larger model your whole history takes tens of seconds, and sends it off your machine.

The Kaineros desktop app answering a PersonaMem-v2 persona: a personalised, second-person recommendation that draws on your late-night binge-watching habit and pollen allergy; the three pages it read listed at right; a 1.9-second response time; and a low-poly face beside the chat.
Answering a PersonaMem-v2 persona in 1.9 seconds — reading three compiled pages (listed at right), phrased directly to you, with its reasons shown beneath the answer.

We measured Kaineros against PersonaMem, a benchmark for tracking a user across a long, evolving conversation, three ways — the same questions, scored the same way:

PersonaMem v2 — 5 personas, 129 questions
SetupReadsAccuracyResponse time
Kaineroscompiled wiki0.41~1.4 s
Small modelraw history0.50~28 s
Large modelraw history0.67~28 s
PersonaMem v1 — 5 personas, 49 questions
SetupReadsAccuracyResponse time
Kaineroscompiled wiki0.61~1.6 s
Small modelraw history0.73~23 s
Large modelraw history0.78~23 s

Response time is time-to-first-word, measured. The raw-history rows must read tens of thousands of tokens before the first word; Kaineros reads a handful of compiled pages.

Reading it honestly

It trades a little accuracy for speed, cost, and privacy.

Reading the raw history is more accurate at this length — and Kaineros doesn’t beat it there. What the compiled memory buys is the thing an assistant actually needs to be usable:

And the gap is where the work now goes: teaching the fast search to reach the raw detail it needs, on demand, without giving up the speed.

Caveats

← back to kaineros.com