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.
-
“Hot Schema changes are a powerful capability which we use to minimize downtime during system-wide upgrades and shorten our application/schema development cycle.”
—Xing Li, CTO, FictionPress 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: bradley
The TokuDB storage engine for MySQL employs Fractal Tree technology. We’ve been planning to write a white paper explaining how fractal tree indexing works, but haven’t gotten to it yet. In the mean time, here are links to some academic…
The talk I gave at the Percona Performance Conference at the MySQL
Users Conference in April 2009 can be found
at http://tokutek.com/presentations/kuszmaul-mysqluc-percona-09-slides.pdf.
This talk provides some examples where covering indexes help, and
then describes a performance model that can…
Every time I visit the Sun Santa Clara Campus, I’m reminded of Mel
Brooks’s movie “High Anxiety”. The campus was known as The Great
Asylum for the Insane in the 19th century, and even includes a tower.
High Anxiety,
whenever…
Posted by Bradley C. Kuszmaul and David Wells
Executive Summary: A MySQL straight join can speed up a query that is very similar to TPC-H Q2 by a factor of 159 on MySQL.
Recently, we began looking at TPC-H performance…
We modified the iiBench benchmark to perform deletions as well as insertions, and compared InnoDB to Tokutek’s Fractal TreeTM storage engine, both running on MySQL 5.1. I’ll post the revised iiBench tarball soon.
Here is what the performance looks like:…
At OpenSQL Camp in November we presented a challenge to insert one billion rows, maintaining indexes, into a MySQL table. The best results we have seen are:
We re-ran iiBench based on Mark Callaghan’s excellent work. We used standard InnoDB engine in MySQL 5.1 without the Google or Percona patches. Our hardware is similar to Mark’s except we used a 6-disk hardware RAID 0, whereas Mark…
A tip of the hat to Mark Callaghan, who suggested I post our my.cnf settings for iiBench.
Instead of fiddling around with the configuration file, we adjusted everything on the command line. Here’s the relevant script from iiBench/scripts/start_mysql.sh:
I’d like to advertise my previous iiBench posting again (now that we are feeding into PlanetMySQL.)

