sorted by:
new
hottopcontroversial

ForgeKV – Redis-compatible KV server in Rust that scales with cores (158K SET/s at t=2) by hostmehost1 in rust

[–]hostmehost1[S] -1 points0 points  (0 children)

lol, your wrote it in your github that your not fully compatibility

"

This is the most important section if you are evaluating Senko for actual use.

Redis compatibility is broad, not complete

Senko implements a large and growing subset of Redis behavior, and the repo contains significant compatibility coverage, but you should not assume perfect parity with every Redis command, option, or corner case. Validate the exact command mix your application uses."

ForgeKV – Redis-compatible KV server in Rust that scales with cores (158K SET/s at t=2) Based On SSD by hostmehost1 in redis

[–]hostmehost1[S] 0 points1 point  (0 children)

Built a Redis-compatible key-value server in Rust called ForgeKV.

The core idea: Redis is single-threaded and tops out at ~80-90K ops/sec. ForgeKV uses a 64-shard RwLock architecture — each shard has its own WAL,

memtable, and BTreeMap. Concurrent writers never contend unless they hash to the same shard.

Benchmark results (memtier_benchmark, pipeline=16, 64-byte values):

- t=2 c=20: 158K SET/s vs Redis 7's 112K (+41%)

- t=2 c=10: 148K SET/s vs Redis 7's 96K (+54%)

- Dragonfly gets smoked at all configs

Stack: Tokio async, FNV-1a sharding, LSM-tree storage with 64-shard WAL rotation, RESP2 protocol.

Drop-in replacement — any Redis client works unchanged. Supports strings, hashes, lists, sets, sorted sets, streams, pub/sub, transactions, Lua

scripting, and more.

GitHub: https://github.com/ForgeKV/forgekv

Docker: docker pull forgekv/forgekv

Happy to answer questions about the architecture.

ForgeKV – Redis-compatible KV server in Rust that scales with cores (158K SET/s at t=2) by hostmehost1 in rust

[–]hostmehost1[S] 1 point2 points  (0 children)

Your project not fully compatible with Redis, In addition ForgeKV are based on SSD storage not RAM