The Tokutek/Sunfish entry into the next America’s Cup promises to bring the America’s cup back to the USA’s east coast. The sailboat, named '; Update Race set time=1 where Team='Tokutek (we’re trying to win using a SQL injection attack) features a single-hull pontoon-type hull carrying a lateen sail mounted to an un-stayed mast. The fiberglass hull carries a crew of one or two. The double-plus secret keel technology features a daggerboard keel, an overall length of 4.22m, a beam of 1.24m, and a hull weight of 59kg. The 6.0m2 mainsail provides a D-PN of 100.7, and an on-board computer comprising an Android in a zip-lock sandwich bag running MySQL with TokuDB.

April 1, 2010, Totutek, Inc., announced the acquisition of Oracle Corporation. “Tokutek has long been a supporter of open-source software” said John Partridge, CEO of Tokutek. “Oracle is an innovative small company the develops database front ends such as MySQL. Tokutek intends to continue developing the MySQL technology and expand our commitment to open-soure software.” Oracle CEO Larry Ellison’s role has not been determined. Other than a statement that the transaction is an all-stock transaction, terms of the transaction were not disclosed.

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:

• Improved handling of a full disk
• Configurable disk space reserve
• Faster group commits
• Faster crash recovery
• Improved SHOW ENGINE STATUS and SHOW PROCESSLIST diagnostics

This new release builds on TokuDB’s core benefits:

• 10x-50x faster indexing for faster querying
• Full support for ACID transactions
• Short recovery time (seconds or minutes, not hours or days)
• Immunity to database aging to eliminate performance degradation and maintenance …

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 lines between operations and analytics”. We agree with that perspective and that blurred line is particularly relevant to the community of advanced web application developers who built on MySQL.

Ian Eure over at Digg articulated the issue well: “The fundamental problem is endemic to the …

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.

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 recovery time (seconds or minutes, not hours or days)
• Immunity to database aging to eliminate performance degradation and maintenance headaches
• 5x-15x data compression for reduced disk use and lower storage costs

Because of its high indexing performance and transaction support, TokuDB is well suited to Web applications that must simultaneously store and query …

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 first experiment, I compared recovery times when both storage engines (TokuDB and InnoDB) were inserting at maximum rates. In that experiment, following a power cord pull and server restart, TokuDB recovered in 501s, InnoDB in 18505s. In …

Last week Tokutek released version 3.0.0 of TokuDB, adding ACID transactions to its list of features. This post discusses an experiment we ran to measure recovery time following a system crash.

In summary, while actively inserting records into a MySQL database using iiBench, we compared the time to recover from a power-cord pull for both InnoDB and TokuDB.

This is by no means an exhaustive look at recovery performance, but does illustrate the benefits of …

Tokutek is pleased to announce the beta launch of TokuDB for MySQL, version 3.0. Many of our customers have asked for  transaction capabilities to provide the data integrity their businesses require and in this release we provide:

• Full support for ACID compliant transactions
• Fast recovery time (seconds or minutes, not hours or days)

As with previous versions, v3.0 Beta gives our customers these benefits:

• 20x-50x faster indexing for faster querying
• Immunity to database aging to eliminate performance degradation and maintenance headaches
• 5x-15x data compression for reduced disk use and lower storage costs

Because of its high indexing performance and transaction support, TokuDB is well suited to Web applications that must simultaneously store and …

Last spring, we added a feature that allows the user to see the progress of writes in a statement. Vadim liked it. In 2.2.0, in “show processlist”, we add progress information on reads.

Here is an example of what “show processlist” displays on an update:

mysql> show processlist \G
*************************** 1. row ***************************
Id: 1
User: root
Host: localhost
db: test
Command: Query
Time: 7
State: Queried about 1576008 rows, Updated about 197000 rows
Info: update foo set a=9 where a=8

Here is an example of what “show processlist” displays on an insert that requires a query:

mysql> show processlist \G
*************************** 1. row ***************************
Id: 1
User: root
Host: localhost
db: test
Command: Query
Time: 6
State: Queried about 1542001 rows, Inserted about 771000 …