Announcing TokuDB v6.1

TokuDB v6.1 is now generally available and can be downloaded here.

New features include:

The TokuDB storage engine is now available with all the additional functionality of MariaDB 5.5.

Hot column addition/deletion was present in TokuDB v6.0 for MySQL 5.1 and MariaDB 5.2, but not in MySQL 5.5. This feature is now present in all MySQL and MariaDB versions of TokuDB.

TokuDB has always been a great performer on range scans and workloads where the size of the working data set is significantly larger than RAM. TokuDB v6.0 improved the performance of in-memory point queries at low levels of concurrency. TokuDB v6.1 further increased the performance at all concurrency levels.
The following graph shows our sysbench.oltp.uniform performance on an in-memory data set (16 x 5 million row tables, server is 2 x Xeon 5520, 72GB RAM, Centos 5.8)

TokuDB v6.0 offered 4 choices of compression algorithms for each table (uncompressed, zlib, quicklz, and lzma). Changing the compression of an existing table was a blocking operation in TokuDB v6.0 as the table was copied into a new table using the chosen compression. This change is now performed online and the table is fully available for select, insert, update, and delete operations during the transition.

Tables created without specifying “engine=” now utilize the TokuDB storage engine. Prior to this change MyISAM wast he default in MySQL 5.1 and MariaDB 5.2, InnoDB was the default in MySQL 5.5 and MariaDB 5.5.

If the engine specified in a table create statement is unavailable, an error is returned to the user and the table is not created. The prior behavior was to create the table with the default storage engine and issue a warning to the user.

PlanetMySQL Voting: Vote UP / Vote DOWN