Yearly Archives: 2010

See us at the O’Reilly MySQL Conference...

Posted on by John Partridge

At this year’s O’Reilly MySQL Conference we will be showing the latest version of our MySQL storage engine, TokuDB v3.1.
Come visit us at Table T1 in the OEM section of the Exhibit Hall.
We will be talking about…

Leave a comment

Announcing TokuDB v3.1

Posted on by John Partridge

Tokutek is pleased to announce immediate availability of TokuDB for MySQL, version 3.1. It is designed for continuous querying and analysis of large volumes of rapidly arriving and changing data, while maintaining full ACID properties.
TokuDB v3.1′s new functionality includes:…

Leave a comment

The 451 Group reports on TokuDB v3.0 for MySQL

Posted on by John Partridge

Matt Aslett over at The 451 Group has written a Market Development report entitled “Tokutek delivers ACID transaction support with TokuDB version 3.0.” Get the full report and you can try out The 451 Group’s services for free by…

2 Comments

80x insertion speedup for Profile...

Posted on by John Partridge

One of Profile Technology Ltd.‘s most popular applications is their Advanced Search function for Facebook. Find out how TokuDB v3.0 dramatically increased their insertion speed performance in our new Case Study.

Comments Off

Announcing General Availability of TokuDB v3.0...

Posted on by John Partridge

Tokutek is pleased to announce immediate availability of TokuDB for MySQL, version 3.0. It is designed for continuous querying and analysis of large volumes of rapidly arriving and changing data, while maintaining full ACID properties.
TokuDB v3.0 combines our…

Leave a comment

Recovery Times – Part Deux

Posted on by dave

In a follow-up experiment to an earlier post on TokuDB recovery times, I tried to create a better apples-to-apples comparison to InnoDB recovery time. If I measure recovery times when both DBs are doing the same amount…

Leave a comment

High Insertion Rates into a TokuDB Table with...

Posted on by Rich Prohaska

We recently made transactions in TokuDB 3.0 durable. We write table changes into a log file so that in the event of a crash, the table changes up to the last checkpoint can be replayed. Durability requires the log file…

Comments Off