We're the team behind HotKV, a Redis-compatible in-memory data store. We just published a throughput comparison with Redis, Valkey, and Dragonfly, along with the scripts and raw results. On a 192-vCPU AWS instance, HotKV measured 93.1M GETs/sec and 61.5M SETs/sec. Dragonfly was the closest on those two commands, at 27.5M GETs/sec and 25.4M SETs/sec. Across the AWS, Google Cloud, and Azure runs, HotKV had the highest median throughput on at least 11 of 12 commands per instance. Each engine ran alone on the same server for its comparison. We used separate load generators, 256-byte values, a pipeline depth of 30, and persistence off. Each number is the median of three runs. We treated PING as a tie where the load generator capped both HotKV and Dragonfly. Redis and Valkey are commonly scaled by sharding keys across multiple primary processes, so we also tested all four engines in cluster mode on the same three AWS servers. Redis and Valkey each ran 40 primary processes per server. HotKV and Dragonfly each ran one 40-thread process per server. Here are three results from the cluster test, in millions of operations per second: Command HotKV Redis Valkey Dragonfly GET 92.3 57.3 52.9 22.5 SET 76.1 55.0 48.5 25.2 APPEND 35.0 41.7 40.9 10.4 HotKV recorded the highest measured throughput on 8 of 9 commands in that cluster setup. Redis and Valkey both came out ahead on APPEND. The cluster test used 256-byte values, a pipeline depth of 100, and persistence off. We also ran a separate latency test on a single AWS server, using 256-byte values and a pipeline depth of 1. We stepped up the request rate and compared latency at rates each engine could sustain. At about 200,000 GETs/sec with 816 connections, we measured: Latency HotKV Redis (8 I/O threads) Valkey (8 I/O threads) Dragonfly p50 0.25 ms 0.55 ms 1.11 ms 0.25 ms p99 0.59 ms 1.11 ms 2.15 ms 1.34 ms With 48 connections at about 50,000 GETs/sec, HotKV, Dragonfly, and Redis with 8 I/O threads all measured 0.28 ms at p99. At the higher end of the 816-connection test, HotKV and Dragonfly both sustained about 1.6 million GETs/sec, with p99s of 0.64 ms and 0.71 ms respectively. If you'd like to try HotKV on your own workload, HotKV Cloud is free during early access for everyone accepted. You can apply without a card or any payment details. We'd like the next benchmark to look more like an application workload. If you've had to scale a Redis or Valkey deployment, what hit the limit first?   submitted by   /u/HotKV-Ltd [link]   [comments]