Redis-compatible systems / published benchmarks
Compare the measurements.
Explore throughput and tail latency under the reported test conditions.
CacheArena is owned by Lavik. These initial results were measured and published by Lavik, and have not been independently replicated.
Our approach to fairness01 / Explore the results
Different workloads. Different answers.
Lavik: values on NVMe SSD. Redis and Valkey: values in DRAM. Lavik still uses DRAM for its key index and runtime state.
10M keys / Read-only GET
Throughput by system
Each row shows that system’s highest measured throughput; connection counts can differ. QPS is rounded for display; the CSV preserves source precision.
Value-capacity cost / illustration
A different storage medium.
A different cost equation.
at a 20:1 DRAM / NVMe SSD price ratio
Lavik places values on NVMe SSD while Redis and Valkey use DRAM. This model illustrates the storage economics alongside the measured throughput above.
Lavik’s cost methodologyRelative value-capacity cost · Redis = 100%
Lavik’s 5% assumes DRAM costs 20× more per GiB than NVMe SSD. Index memory, runtime memory, replication, and shared server costs are additional. Valkey’s 80% follows the separate 400 GB vs 500 GB memory-use example linked on Lavik’s homepage, at equal DRAM prices. These are not measured costs for the 10M-key benchmark or whole-deployment savings.
The numbers behind the chart
3 configurations · 10M keys| System / version | Throughput ops/sec | p99 ms | p99.9 ms | Connections | Server threads¹ | Evidence |
|---|---|---|---|---|---|---|
| LLavikSPDK · NVMe SSD0.1.0-beta.1 | 1,012,180 | 3.599 | 5.631 | 640 | 16 workers | Source report |
| RRedisDRAM8.8.0 | 976,801 | 4.671 | 8.031 | 1,280 | 16 io-threads | Reused control |
| VValkeyDRAM9.1.0 | 965,697 | 4.543 | 8.159 | 1,280 | 16 io-threads | Reused control |
Redis and Valkey use their best measured I/O-thread configuration for the selected workload by default. AOF and automatic snapshots are disabled. Thread roles and persistence semantics differ. Read the test conditions
¹ Thread counts describe different roles, not equivalent compute. Garnet’s actual thread count is not fixed. All 10M- and 1B-key server processes share a 16-logical-CPU affinity limit.
Inspect the full connection sweepEvery measured point for the selected thread configurations
Throughput across client connections. The vertical scale starts at zero. Each point is one run.
| System | 80 conn. | 160 conn. | 320 conn. | 640 conn. | 1280 conn. |
|---|---|---|---|---|---|
| Lavik SPDK · NVMe SSD | 390,494.48 | 609,160.94 | 803,016.34 | 1,012,179.91 | 940,713.30 |
| Redis DRAM | 424,582.46 | 574,701.86 | 769,130.32 | 919,798.51 | 976,800.89 |
| Valkey DRAM | 544,238.03 | 692,905.05 | 826,689.24 | 897,768.48 | 965,696.86 |