MyRocks vs TokuDB

MyRocks Vs TokuDB

I have not yet fully tested MyRocks, but i will just briefly write about some finding based on my study of both engines. I have to mention though that i have experience with TOkuDB and played a lot with it in a test environment.

Both are designed for environments with heavy writes, and both perform very poorly in read heavy environments compared to InnoDB [1].

So the benchmarks would be to compare write performance. I suspect the main difference would lie in TokuDB's Fractal Trees and MyRocks LSM index algorithms - like how InnoDB uses B-Tree.

MyRocks LSM was designed for disks, but it is said to be well effective on SSD [1].

Some things to know about MyRocks? include:

• LSM might use more CPU per query because more data structures can be checked to satisfy a query.
• Better efficiency on writes and worse efficiency from reads with an LSM compared to a B-Tree.

I did some study on TokuDB where i listed some things to know about it, including:

• maintains performance when data set gets bigger than memory.
• Better efficiency on writes and worse efficiency from reads

REFERENCES

[1] http://smalldatum.blogspot.tw/2016/01/summary-of-advantages-of-lsm-vs-b-tree.html
[2] http://smalldatum.blogspot.tw/2014/07/benchmarking-leveldb-family.html