TurboKV: Insanely fast Rust key-value store

Post by a2ff6eeb0 » Sat, Aug 29, 2026, 4:40 AM UTC

rgbimbochamp wrote: post #8

stingraycharles wrote: post #7

Earlier quoted context omitted.

Yeah this should be benchmarked against other systems that have flush() disabled. mmap is nice but it doesn’t support durable semantics in the way that we usually mean with databases. if a write is acknowledged it should not be forgotten, which is not what this is.

You're right, that mode provides process crash recovery, not power-loss durability. The benchmark compares it against fjall’s equivalent buffered-WAL mode.

Post by AtlasBarfed » Sat, Aug 29, 2026, 4:54 AM UTC

Post by [deleted] » Sat, Aug 29, 2026, 5:05 AM UTC

rgbimbochamp wrote: post #3

nine_k wrote: post #2

I suppose the insane speed is due to this: > TurboKV's persisted Bloom-filter format uses hardware AES. Also, built-in LZ4 compression. I would expect SIMD to be used for scans.

Those help but the main write speed gain is the WAL, that uses preallocated mmap segments to avoid a write(2) per durable mutation while preserving crash recovery. AES hashing mainly helps Bloom filter point lookups and LZ4 mainly helps SSTable I/O. Scans benefit indirectly, but don’t yet use a custom SIMD merge loop.

Post by yeasin-arafat » Sat, Aug 29, 2026, 5:44 AM UTC

Post by karen4830 » Sat, Aug 29, 2026, 5:46 AM UTC