Our customers are choosing MariaDB more and more frequently for their most demanding database applications. We are delighted to help raise MariaDB performance to the next level by making TokuDB available on this new platform. One of our customers, who wishes to remain unnamed for the present time, chose MariaDB + TokuDB for a 3 TB database after having evaluated other MySQL alternatives and finding them unacceptably slow.

TokuDB continues to be the ideal choice for complex / high-volume applications that must have fast response times and that must simultaneously store and query large volumes of rapidly arriving data:

• Social Networking
• Real-time clickstream analysis
• Logfile Analysis
• eCommerce Personalization
• High-speed Webcrawling

TokuDB has always been available for MySQL and we are pleased to add support now for MariaDB. As with our MySQL version, the MariaDB version uses our high-performance Fractal Tree™ indexing to provide a unique combination of capabilities:

• 10x-50x faster indexing for faster querying
• Immunity to database aging for eliminating query slow-downs (no more dump / reload)
• 5x-15x data compression for reduced disk use and lower storage costs
• Multi-threaded Fast Loader for reduced load times
• Full ACID transaction support
• Fast recovery time (seconds or minutes, not hours or days)

• Social Networking
• Real-time clickstream analysis
• Logfile Analysis
• eCommerce Personalization
• High-speed Webcrawling

TokuDB v4.1.1 replaces TokuDB v4.1.0 and is recommended for all users. (We found a bug in v4.1.0 and have withdrawn it from our website). The new version has all of v4.1.0′s new features, including support for SAVEPOINT and an even better Fast Loader. As always, this release uses our high-performance Fractal Tree™ indexing to provide a unique combination of capabilities:

• 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 headaches
• 5x-15x data compression for reduced disk use and lower storage costs

New in TokuDB v4.0 is our multi-threaded Fast Loader. Capable of utilizing all available CPU cores, the Fast Loader greatly accelerates creating a new index or initializing a database with a bulk load. On an 8 core machine, loading operations speed up by over 4x and with 16 cores the acceleration is even greater.

Other improvements in v4.0 include:

• Shorter Logfiles – The logs needed for ACID transactions are now considerably
  smaller. In addition to saving disk space, smaller logs means faster recovery in many cases.
• Faster Logfile Reclamation – When a transaction commits, the space associated with logging for that transaction is reclaimed more quickly. This helps keep disk space requirements to a minimum.
• Support for READ COMMITTED isolation level – Fulfills a very popular customer request.

This new release builds on TokuDB’s unique combination of capabilities:

• 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 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 large volumes of rapidly arriving data, including:

• Logfile Analysis
• High-speed Webcrawling
• Real-time clickstream analysis
• Social Networking
• eCommerce Personalization

Here are the details.

Come visit us at Table T1 in the OEM section of the Exhibit Hall.

We will be talking about how TokuDB can dramatically improve performance for:

• Social Networking applications
• eCommerce Personalization
• Logfile Analysis
• High-speed Webcrawling
• Real-time clickstream analysis

Customers pick TokuDB for:

• 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 headaches
• 5x-15x data compression for reduced disk use and lower storage costs

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 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 large volumes of rapidly arriving data, including:

• Social Networking
• eCommerce Personalization
• Logfile Analysis
• High-speed Webcrawling
• Real-time clickstream analysis

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 relational database mindset, which places the burden of computation on reads rather than writes. This is completely wrong for large-scale web applications, where response time is critical.”

Because of the B-tree index’s inability to perform at high speed simultaneously on read-intensive and write-intensive workloads, database usage has clumped around the two ends of the trade-off: read-intensive OLAP and write-intensive OLTP. Those are big “clumps” indeed and the valley in between – where advanced MySQL based web applications reside – is sizable.

At Tokutek we are serving those applications with Fractal Tree indexing and beginning to fill the valley. Or as Mark Callaghan noted in his MySQL+memcached piece, “Write-optimization has finally arrived for MySQL with the availability of TokuDB.”

TokuDB v3.0 combines our long-standing performance advantages with ACID compliant transactional integrity: