From 52226341de2bf34a3c1c16e07d6dda785b48dde8 Mon Sep 17 00:00:00 2001 From: Chris Lu Date: Mon, 9 Mar 2026 19:55:27 -0700 Subject: [PATCH] clarify write batching is crash-safe (client blocks until durable) --- Rust-Volume-Server.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/Rust-Volume-Server.md b/Rust-Volume-Server.md index d288685..80a1616 100644 --- a/Rust-Volume-Server.md +++ b/Rust-Volume-Server.md @@ -175,7 +175,7 @@ The `redb` backend is Rust-only. It provides crash-safe disk-backed needle maps | `/metrics` endpoint | On admin/metrics port | On admin (debug) port | Both serve on admin port, not the main volume port | | Disk monitoring | `sysinfo` package | `sysinfo` crate + `libc` | | | Volume preallocation | `fallocate` on Linux | `fallocate` on Linux via `libc` | Identical behavior | -| Write batching | Synchronous per-request | Async batched write queue (128 batch, mpsc) | Rust batches concurrent writes for higher throughput | +| Write batching | Synchronous per-request | Batched write queue (up to 128, mpsc) | Rust groups concurrent writes to reduce lock acquisitions. Each client still blocks until its write is durable — no crash-safety difference | | Streaming reads | Files > 1MB | Files > 1MB via `spawn_blocking` | Same threshold, async I/O | ### Extra CLI Flags (Rust only)