Redis vs Valkey vs Dragonfly vs KiviDB

A week after the last run, the same 64-core Graviton3 with KiviDB 1.2.0, which reworked how it stores a key, and Dragonfly 2.1. Memory adds random-byte values, the next million keys and each engine's total RSS beside the ranked number.

KiviDB 1.2.0 cut its memory per key by 44% and came within 8 bytes a key of Dragonfly 2.1, which kept the p99 and memory sections, while KiviDB kept pipelining by 31% and out-served Dragonfly on small values in every pass.

Small value throughput

SET/GET mix (1:10 ratio) with 100-byte values, pipeline depth 1. RESP2, no TLS.

Dragonfly 1.42M ops/s at the lowest p99 (0.41 ms); KiviDB 1.51M (0.45 ms), the most ops/s on every pass; Valkey 177K (2.10 ms); Redis 176K (2.11 ms)