We're the team behind HotKV, a Redis-compatible in-memory data store. We ran a comparison with Redis, Valkey, and Dragonfly on a c4d-standard-384 in us-central1-a. The interesting limit in this run was the network.

HotKV measured 80.5M GETs/sec and 62.5M SETs/sec with 256-byte values. Dragonfly was the closest on those commands at 9.0M GETs/sec and 10.1M SETs/sec. These figures describe one process per engine on this VM.

With two separate h4d-standard-192 load generators, iperf3 measured about 172 Gbps outbound and 176 Gbps inbound. During HotKV's GET run the server NIC counters showed about 173 Gbps outbound, so the result reached the measured network ceiling. Several write commands also approached the inbound limit.

We ran each engine separately on the same server, using memtier_benchmark, pipeline depth 30, persistence off, and the median of three runs. HotKV was compiled with -march=native for the CPU. Redis 8.10.3, Valkey 9.1.3, and Dragonfly 2.0.2 used their upstream release build settings.…