Supporting methodology and editorial history

Retained October 9, 2026. These passages preserve scope and revision history; they are not new test results. Source references remain in the article.

The historical client decodes read responses but does not compare each returned value with an expected value. Original run logs and correctness evidence remain part of the reconciliation. These are promising recorded throughput results, not yet a newly validated performance guarantee.

8DB reported 19.99M ops/s at batch size 128; the same-host campaign recorded 3.087M GET/s for Redis at pipeline depth 128. The numerical gap is substantial. Payload, key-space, exact commands and trial-selection reconciliation remain incomplete, so these are historical configuration references, not a matched competitive speedup.[1,4]

Both figures concern key-value reads: ask for a key, get its associated value. For 8DB, an omnimodal database, this May 2026 campaign exercised its in-memory binary batch path on one 32-vCPU AMD server. Original-trial and correctness reconciliation remains open.[1]