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 visiting http://the451group.com/apply/apply.php.
Matt observes that, “While TokuDB is effectively an operational database technology, it does blur the [...]

2 comments | Continue Reading

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.

1 comment | Continue Reading

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 long-standing performance advantages with ACID compliant transactional integrity:

10x-50x faster indexing for faster querying
Full support for ACID transactions
Fast [...]

0 comments | Continue Reading

Recovery Times – Part Deux

Published on 13 January 2010 by dave in TokuView

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 of work, TokuDB requires only 2s to recover from a crash, compared to 1020s for InnoDB.

Background

In the [...]

0 comments | Continue Reading

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 to be fsync’ed when a transaction is committed. Unfortunately, fsync’s are not [...]

0 comments | Continue Reading