As somebody that has pushed some proprietary services to 4.5M RPS at low-latency (~850-900us p99 in the same dc) I'm a bit skeptical about the "5M+ GET/s" claim.
I'd like to see how the benchmark was performed, on what hardware, with what client-side latencies (ok p50, but what about p99/p99.9?).
A few tables with no methodological details sound a bit fishy.
The Redis-compatible server is based on Feox DB, which is an embedded KV Store in Rust.
https://github.com/mehrantsi/feoxdb
As somebody that has pushed some proprietary services to 4.5M RPS at low-latency (~850-900us p99 in the same dc) I'm a bit skeptical about the "5M+ GET/s" claim.
I'd like to see how the benchmark was performed, on what hardware, with what client-side latencies (ok p50, but what about p99/p99.9?).
A few tables with no methodological details sound a bit fishy.
Feel free to test for yourself :)
Test was done using Redis benchmark for 1M random keys, 50 clients, Pipeline depth, 64.
I did this locally on my MBP M3-Max. This gives a little over 2M for Redis and 5.4M for Feox.
redis-benchmark -n 1000000 -r 1000000 -c 50 -P 64 -t SET,GET -q
https://x.com/mltoosi/status/1963599382592590069?s=46
Feox DB itself (the embedded KV behind the server) is quite fast as well. You can also test for yourself or see the criterion benchmark report.
https://feoxdb.com/benchmarks.html
<700ns INSERT and <200ns GET on Feox DB itself.