EmergencyEMERGENCY? Get 24/7 Help Now!

TokuDB Hot Backup Now a MySQL Plugin

 | February 5, 2015 |  Posted In: Tokutek, TokuView

In the recently released TokuDB 7.5.5 the implementation of TokuDB hot-backup moved from a patch to the MySQL Server, to MySQL Plugin.  Why did we make this change? TokuDB hot backup makes a transactionally consistent copy of the TokuDB files while applications continue to read and write these files.  Christian Rober wrote a nice series […]

Read More

TokuDB 7.5.5 is now available

 | January 29, 2015 |  Posted In: Tokutek, TokuView

Tokutek is pleased to announce the general availability of TokuDB 7.5.5. The notable changes since TokuDB 7.5.3 are: Rebased onto MySQL 5.5.41 and MariaDB 5.5.41 to integrate the latest changes Improved TokuDB lock timeout logging Added several optimize table options for TokuDB tables including the ability to throttle the optimize operation, selectively pick indexes to optimize, optimize […]

Read More

Scaling TokuDB Performance with Binlog Group Commit

 | December 17, 2014 |  Posted In: Tokutek, TokuView

TokuDB offers high throughput for write intensive applications, and the throughput scales with the number of concurrent clients.  However, when the binary log is turned on, TokuDB 7.5.2 throughput suffers.  The throughput scaling problem is caused by a poor interaction between the binary log group commit algorithm in MySQL 5.6 and the way TokuDB commits […]

Read More

An Updated Description of Clustering Keys for TokuDB

 | August 6, 2014 |  Posted In: Tokutek, TokuView

Covering indexes can result in orders of magnitude performance improvements for queries. Bradley’s presentation on covering indexes describes what a covering index is, how it can effect performance, and why it works. However, the definition of a covering index can get cumbersome since MySQL limits the number of columns in a key to 16 (32 on […]

Read More

Why TokuDB does not use the ‘uint3korr’ function

 | April 8, 2014 |  Posted In: Tokutek, TokuView

The ‘uint3korr’ function inside of the mysqld server extracts a 3 byte unsigned integer from a memory buffer. One use is for ‘mediumint’ columns which encode their value in 3 bytes. MySQL 5.6 and MariaDB 10.0 claims to have optimized this function for x86 and x86_64 processors. There is a big comment that says:

[…]

Read More

Uninitialized data in the TokuDB recovery log

 | April 3, 2014 |  Posted In: Tokutek, TokuView

A TokuDB MySQL test run with valgrind reported an uninitialized data error when writing into the TokuDB recovery log.

TokuDB should not be storing uninitialized data into its files, so I need to find the the code that neglected to initialize the memory that eventually got written to the recovery log. An update SQL […]

Read More

Lock Escalation and Big Transactions in TokuDB and TokuMX

 | March 27, 2014 |  Posted In: Tokutek, TokuView

We have seen TokuDB lock escalation stall the execution of SQL operations for tens of seconds. To address this problem, we changed the lock escalation algorithm used by TokuDB and TokuMX so that the cost of lock escalation only affects big transactions. We also eliminated a serialization point when running lock escalation. Transactions in TokuDB […]

Read More