Part 5 of 7 · ← Latency under load · Next: Operational simplicity → Part 5. The shortest post in the series, and the least arguable number in it — because memory footprint is about data-structure design, not how hard you drive the client. It's the same on a laptop and on 48 bare-metal cores. The measurement I loaded 1,000,000 keys × 100-byte values into each engine, subtracted the empty-server baseline, and divided by key count: Engine bytes / key ...