Well Kvrocks is on disk, not in memory.

That's true, however the intention to run the benchmark would be against most of the widely used commands and see if there is any command or use case where kividb might be a better fit than kvrocks. strictly speaking from hardware performance, it would certainly beat kvrocks in terms of sheer throughput, but in terms of volume where does it stand would be something interesting to experiment.

Kvrocks is both iirc, since it can cache the rocksdb data in memory.