-
Notifications
You must be signed in to change notification settings - Fork 26
Benchmarks
Regunath B edited this page Nov 20, 2020
·
3 revisions
RocksDB and Badger were evaluated as backing data stores for dkv. Additionally Redis was also evaluated as an out-of-process co-located data store, more for benchmarking purposes rather than as a true backend.
Benchmarking results that lead to data store choices for dkv are captured here : RocksDB, Badger, Redis benchmarks
dkv currently supports/uses RocksDB & Badger in these runtime modes:
- RocksDB - for all Master(Raft Leader and Follower) nodes for its bin log and CDC support. It may optionally be used for Slave nodes too.
- Badger - for all Slave nodes, optionally in diskless (i.e. in-memory only) mode too.
dkv has been benchmarked using YCSB. The benchmarking setup is as follows:
The results are available here: dkv benchmarks