Questions before you start
Practical answers for evaluating Lavik 0.1.0.
Can I use Lavik in my project?
EloqData-authored Lavik code is available under Apache License 2.0. Third-party components retain their own licenses and notices.
Can I use my existing Redis client?
Lavik speaks RESP2 and RESP3 and implements a broad Redis-compatible command surface. Check the commands and operational behavior your application depends on.
Can I run the server directly on macOS?
The published packages target Linux x86_64 and ARM64. Running Lavik requires Linux 6.1 or newer with io_uring enabled and a compatible glibc; release packages are built on Ubuntu 24.04.
On macOS, use a Linux virtual machine or container environment whose kernel and security policy permit io_uring. A Linux environment alone does not guarantee that every required syscall is allowed.
Does the benchmark establish production cost or availability?
The comparison used an AMD EPYC 9V74 server, 125 GiB RAM, six raw NVMe drives, 10 million 1 KiB values, and 30-second measurement windows. Redis persistence was disabled and Lavik defragmentation was paused. These measurements do not establish equivalent crash durability, production cost, or an application SLA.
A successful write response is not a synchronous fsync fence. Evaluate durability, replication, and recovery requirements for your workload.