tokudb 个人整理

最新推荐文章于 2024-05-10 09:35:16 发布

xluren

最新推荐文章于 2024-05-10 09:35:16 发布

阅读量974

点赞数

分类专栏： mysql 文章标签： tokudb

本文链接：https://blog.csdn.net/xluren/article/details/42687345

版权

mysql 专栏收录该内容

5 篇文章 0 订阅

订阅专栏

Has anyone used the TokuDB storage engine for MySQL?

The product web site claims to have a 50x performance increase over other MySQL storage engines (e.g. Innodb, MyISAM, etc). Here are the performance claims http://tokutek.com/downloads/tokudb-performance-brief.pdf

Is this true?

Any personal experiences with this storage engine in use with MySQL?

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.

Completely agree. We have three databases - two around 1.5TB and one 40GB. We've moved the two large ones to TokuDB and have been blown away by it - we're seeing over 15k queries per second (half of that is inserts/updates) on fairly ordinary hardware. Add in online schema maintenance (column addition/drops, index creation/drops) and it's been phenomenal. That said, @Xing is right about using the right tool for the job - we've left the smaller db on InnoDB, as we've found it performs better for smaller workloads. We've been running TokuDB hard in production for 6 months, and had zero problems.

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.