MySQL: Has anyone used the TokuDB storage engine?

If you are storing blobs such as images then don't use tokudb. It has a smaller row size limit.

If you have data that's over 100 million rows, use tokudb.

If you are sensitive to UPDATE speed, don't use tokudb. It has very fast insert but as compared to innodb, slower UPDATE speed and especially if you use INSERT ON DUPLICATE statements.

If you are storing log entries, use tokudb.

If you want to shrink your myisam/innnodb's data usage by more than 5x, then use tokudb. I have personally confirmed that their fractal tree + compression data backend is extremely space efficient.

Rule of thumb, use the best tool for the job. Tokudb blows innodb and myisam out of the waters in specific situations but is not a general replacement db engine for everything under the sky.

Although TokuDB is slow on UPDATE as commented above, it is extremely fast on REPLACE. Usually you can substitute UPDATEs with REPLACE INTO instead. I use TokuDB on tables of up to 18 Billion rows and nothing else comes close, it's at least 100 times faster than innodb for random inserts on big tables.

I have the same question. I did find a fairly decent comparison of TokuDB against Innodb

http://www.pythian.com/news/5139/testing-tokudb-faster-and-smaller-for-large-tables/

However, I am interested in any other experiences that others may have had with TokuDB or any other similar storage engine for MySQL.

Another review herehttp://www.mysqlperformanceblog.com/2009/04/28/detailed-review-of-tokutek-storage-engine/