We're the team building HotKV, a Redis-compatible in-memory data store. We tested it alongside Redis, Valkey, and Dragonfly on one 160-vCPU Azure D160alds_v7, using three separate client VMs to generate the load.

HotKV measured 36.6M GETs/sec and 50.5M SETs/sec. Dragonfly was closest on these two commands, at 13.4M GETs/sec and 15.0M SETs/sec.

The network was an important part of this result. We measured 78.4 Gbps outbound and at least 131.7 Gbps inbound with iperf3. GET sends values out, so it approached the outbound ceiling. Writes receive values, which helps explain why SET throughput could exceed GET throughput in this setup.

Each engine ran alone on the same VM. We used 256-byte values, pipeline depth 30, persistence off, and the median of three runs. HotKV was compiled for this CPU with -march=native. The other engines used their upstream release build settings.…