Tokutek is pleased to announce the general availability of TokuDB for MySQL, version 2.2.0.
At Tokutek, Rich Prohaska used Gearman to automate our nightly build and test process for TokuDB for MySQL. Rich is busy working on TokuDB, so I’m writing up an overview of the build and test architecture on his behalf.
Build and Test Process
Rich created a script, nightly.bash, that gets kicked off every night as a [...]
We often hear from customers and MySQL experts that fragmentation causes problems such as wasting disk space, increasing backup times, and degrading performance. Typical remedies include periodic “optimize table” or dump and re-load (for example, see Project Golden Gate). Unfortunately, these techniques impact database availability and/or require additional administrative cost and complexity. [...]
I saw Mark Callaghan’s post, and his graph showing miss rate as a function of cache size for InnoDB running MySQL. He plots miss rate against cache size and compares it to two simple models:
A linear model where the miss rate is (1-C/D)/50, and
A inverse-proportional model where the miss rate is D/(1000C).
He seemed happy [...]
We’re supporting the OpenSQL Camp, which will be held in Portland on November 14.
One of my objectives for the camp is to make progress on a universal storage engine API, to make it possible to use the same storage engines in MySQL, PostgreSQL, Ingres, or any other database. I’m also looking forward [...]
Sorting a Terabyte in 197 seconds
I just returned from The 21st ACM Symposium on Parallelism in Algorithms and Architectures (SPAA), held in Calgary, where I gave a talk about my entry to the sorting contest. I sorted 1TB in 197s on a 400-node machine at MIT Lincoln Laboratory, a record which still stands today. [...]
Tokutek® announces the release the release of the TokuDB storage engine for MySQL®, version 2.1.0. This release offers the following improvements over our previous release:
Faster indexing of sequential keys.
Faster bulk loads on tables with auto-increment fields.
Faster range queries in some circumstances.
Added support for InnoDB.
Upgraded from MySQL 5.1.30 to 5.1.36.
[...]
In our last post, Bradley described how auto increment works in TokuDB. In this post, I explain one of our implementation’s big benefits, the ability to combine better primary keys with clustered primary keys.
In working with customers, the following scenario has come up frequently. The user has data that is streamed into the table, in [...]
In this post I’m going to talk about how TokuDB’s implementation of auto increment works, and contrast it to the behavior of MyISAM and InnoDB. We feel that the TokuDB behavior is easier to understand, more standard-compliant and offers higher performance (especially when implemented with Fractal Tree indexes).
In TokuDB, each table can have an [...]
On April 9-10 the National Science Foundation hosted the Workshop on the Science of Power Management (SciPM 2009), where I gave an invited talk. Here I give a brief summary of my talk along with a pointer to the slides.
The talk describes how MySQL with TokuDB can provide a path to more energy-efficient database implementations. [...]
