Quick start: from download to your first keys

2. Start and connect

The same startup script works with Minimal and Standard. It uses kernel TCP / io_uring, a disposable 512 MiB file, and the loopback address 127.0.0.1:6379. The two workers each have a 64 MiB registered-buffer budget. Leave this terminal running while you connect from a second terminal.

set -euo pipefail
if [ ! -x ./lavik ]; then
  echo "Run this from the extracted Lavik package directory (the folder containing ./lavik)." >&2
  exit 1
fi
mkdir -p /tmp/lavik-example
if [ ! -e /tmp/lavik-example/data ]; then
  fallocate -l 512M /tmp/lavik-example/data
fi
./lavik --bind 127.0.0.1 --port 6379 --metrics-port 0 \
  --network kernel --storage uring \
  --threads 2 --no-pin-workers --registered-buffer-mb-per-worker 64 \
  --shutdown-checkpoint --data-file /tmp/lavik-example/data \
  --log-dir /tmp/lavik-example/logs

$ redis-cli -h 127.0.0.1 -p 6379 --raw PING
PONG

$ redis-cli -h 127.0.0.1 -p 6379 --raw SET greeting 'hello from Lavik'
OK

$ redis-cli -h 127.0.0.1 -p 6379 --raw GET greeting
hello from Lavik

$ redis-cli -h 127.0.0.1 -p 6379 --raw HSET user:42 name Ada
1

$ redis-cli -h 127.0.0.1 -p 6379 --raw HGET user:42 name
Ada

3. Stop and restart

Press Ctrl-C in the server terminal to stop Lavik. To restart, run the same startup script from the same extracted package directory. The script keeps the existing data file instead of allocating it again. The example uses /tmp/lavik-example for disposable data; /tmp can be cleared by the operating system. Choose persistent storage before storing anything you need to keep.

Why ./lavik, rather than lavik?

Extracting an archive does not add its folder to your shell’s PATH. ./lavik explicitly runs the binary in the current directory. A systemd service is optional process management; it does not fix command lookup. Keep using ./lavik here. For an eventual service, use an absolute executable path and a persistent data location rather than this demo directory.

If startup fails

If ./lavik is not found, return to the extracted directory shown in step 1. A GLIBC or shared-library error usually means the OS runtime or Standard dependencies do not match the package requirements. io_uring initialization errors require checking the Linux kernel and sandbox restrictions. If port 6379 is in use, stop your own conflicting demo or choose another port for both the server and redis-cli.

What was actually verified

The displayed startup script and client commands are executed against the exact beta package in Linux Docker, starting in the extracted binary directory with no Lavik entry on PATH. The verification also checks a separate value after a graceful shutdown and restart. The package checks cover Minimal and Standard using kernel TCP / io_uring. They do not exercise an SPDK NVMe device, measure performance, or simulate power loss.

A successful write response is not a synchronous fsync fence. Evaluate durability, replication, and recovery requirements for your workload.