New TokuDB v5.2
TokuDB® v5.2 is a drop-in replacement for InnoDB that scales MySQL® from GBs to TBs while improving insert speed, query performance, compression, and online schema flexibility. Uses standard SQL and supports ACID and MVCC.
-
“For any IO bound workload it will make your day.”
—Stephane Varoqui, Principal Consultant, SkySQL Archive
- February 2012
- January 2012
- December 2011
- November 2011
- October 2011
- September 2011
- August 2011
- July 2011
- June 2011
- May 2011
- April 2011
- March 2011
- February 2011
- January 2011
- December 2010
- November 2010
- September 2010
- August 2010
- July 2010
- June 2010
- May 2010
- April 2010
- March 2010
- February 2010
- January 2010
- December 2009
- November 2009
- October 2009
- September 2009
- August 2009
- July 2009
- June 2009
- May 2009
- April 2009
- March 2009
- January 2009
- December 2008
- April 2008
- March 2008
- February 2008
- January 2008
Author Archives: Martin Farach-Colton
TokuDB® v5.2, the latest version of Tokutek’s flagship storage engine for MySQL and MariaDB, is now available.
This version offers performance enhancements over previous releases, especially for multi-client scale up and point queries, and extends the cases where ALTER TABLE…
Indexes can reduce the amount of data your query touches by orders of magnitude. This results in a proportional query speedup. So what happens when you define a nice set of indexes and you don’t get the performance pop you…
Yesterday, Percona held Percona Live NYC, which they describe as an “intensive one-day MySQL summit.” They meant it. It was like drinking from a firehose. There was too much for me to give a complete report, so I’d like…
OldSQL DBs based on B-trees have some well-known problems and workarounds. TokuDB is a NewSQL storage engines based on Fractal Tree indexing, so the natural question is how InnoDB practice translates into TokuDB. This post gives a quick overview.…
I’ve recently been blogging about how partitioning is a poor man’s answer to covering indexes. I got the following comment from Jaimie Sirovich:
“There are many environments where you could end up creating N! indices to cover queries for…
On April 1st, the Department of Computer Science at Rutgers University, where I am a professor, held an open house. I gave a talk called “Elephants on a Trapeze: Keeping Big Data Agile”.
The talk is an introduction to…
Why do B-trees need “Tricks” to work?
Marko Mäkelä recently posted a couple of “tips and tricks” you can use to improve InnoDB performance. Tips and tricks. A general purpose relational database like MySQL shouldn’t need “tips and tricks”…
Hot Column Addition and Deletion (HCAD)
In the previous HCAD post, I described HCAD and showed that it can reduce the downtime of column addition (or deletion) from 18 hours to 3 seconds. In fact, the downtime of InnoDB…
From 31 minutes to 2 seconds
Hot Indexing Overview
TokuDB v5.0 introduces several features that are new to the MySQL world. Recently, we posted on HCAD: Hot Column addition and Deletion. In this post, we talk about Hot…
From 18 hours to 3 seconds!
Hot Column Addition and Deletion (HCAD) Overview
TokuDB v5.0 introduces several features that are new to the MySQL world. In this series of posts, we’re going to present some information on these features:…

