Performance, in context

Near in-memory performance. With the conditions attached.

Results from the 2026-09-18 SPDK report. Lavik uses the downloaded v0.1.0-beta.1 standard package; Redis and Valkey controls reuse an earlier sweep on the same hosts.

Peak throughput · requests / second
Lavik 0.1.0 SPDK1,012,180
p99 3.599 ms
Redis 8.8.0976,801
p99 4.671 ms
Valkey 9.1.0965,697
p99 4.543 ms

The experiment

AMD EPYC 9V74 server, approximately 126 GiB RAM, six NVMe drives, 10 million 1 KiB values, pipeline=1, and 30-second measurement windows. Lavik uses the beta release with SPDK and kernel TCP. Redis and Valkey controls reuse an earlier sweep on the same hosts, with persistence disabled. Each point was measured once; these results do not establish equivalent crash durability or an application SLA.

The sweep covers 80–1,280 connections. Lavik peaks at 640 connections for GET and 1,280 for SET; Redis and Valkey peak at 1,280. Redis uses 16 I/O threads; Valkey uses 16 for GET and 8 for SET; Lavik uses 16 workers. Each p99 corresponds to the selected throughput peak.

Tested Lavik commit: 3955b98d43b312324aa8d52775df52cfb111c0d0

Read the full report and limitations