I compared InnoDB without compression, InnoDB with 8k
compression, TokuDB with quicklz compression.
Uncompressed datasize is 115GiB, and cachesize
is 12GiB for InnoDB and 8GiB +
4GiB OS cache for TokuDB.

Today Percona announced the immediate availability of 24/7,
enterprise-class support for MongoDB and TokuMX.
The new support service helps organizations achieve maximum
application performance without database bloat. Customers have
round-the-clock access (365 days a year) to the most trusted team
of database experts in the open source community.

The news means that Percona now offers support across the entire
open-source database ecosystem, including the entire LAMP stack
(Linux, Apache, MySQL, and PHP/Python/Perl), providing a single,
expert, proven service provider for companies to turn to in good
times (always best to be proactive) – and during
emergencies, too.

Last week I wrote up my thoughts about the Percona acquisition of
Tokutek from the perspective of TokuDB and TokuMX[se]. In this third blog of the trilogy
I'll cover the acquisition and the future of the Fractal Tree
Index. The Fractal Tree Index is the foundational technology upon
which all Tokutek products are built.

So what is a Fractal Tree Index? To quote the Wikipedia page:"a Fractal Tree index is a tree data structure that keeps data
sorted and allows searches and …

Again, when I'm writing up something that I was very involved
with in the past I think it's important to disclose that I worked
at Tokutek for 3.5 years (08/2011 - 01/2015) as VP/Engineering
and I do not have any equity in Tokutek or Percona.

Since much of the MySQL crowd might be hearing about Tokutek's
"other products" for the first time I'll provide a little history
of both of the products before I dive in deeper.

Two weeks ago Percona announced it's acquisition of Tokutek
(April 14, 2015). The analyst coverage was a bit fluffy for my
liking, but I decided to give it some time and see if anything
"meaty" would come along, and ... it hasn't. The sheer number of
tweets on Twitter was impressive, which makes
me hopeful that the acquisition raised awareness to the Tokutek
technologies and that the Tokutek products have a found a good
home

I've been thinking a lot about the future of the Tokutek
technologies over these same two weeks and want to share them
publicly. I'm going to cover TokuDB in this blog post, TokuMX in
a few days, and finally Fractal Tree Indexes a few days later.
[Full disclosure: I worked at Tokutek for 3.5 years (08/2011 -
01/2015) as VP/Engineering and I do not have any equity in
Tokutek or Percona]

It is my pleasure to announce that Percona has acquired Tokutek
and will take over development and support for TokuDB® and
TokuMX™ as well as the revolutionary Fractal Tree® indexing
technology that enables those products to deliver improved
performance, reliability and compression for modern Big Data
applications.

At Percona we have been working with the Tokutek team since 2009,
helping to improve performance and scalability. The TokuDB
storage engine has been available for Percona Server for about a
year, so joining forces is quite a natural step for us.

Fractal Tree indexing technology—developed by years of data
science research at MIT, Stony Brook University and Rutgers
University—is the new generation data structure which, for many
workloads, leapfrogs traditional B-tree technology which was
invented in 1972 (over 40 years ago!). It is also often
…

If you haven’t already heard, on the Tuesday morning of the 2015
Percona Live MySQL Conference and Expo it was announced that
Tokutek is now part of the Percona family. This means
TokuDB® for MySQL, and TokuMX™ for MongoDB are Percona products
now; and that the Tokutek team is now part of the Percona
team.

Percona’s well-deserved reputation for unparalleled customer
service and support in the MySQL market makes them the perfect
home for Tokutek’s ground-breaking products. And with the
Tokutek acquisition, Percona can expand and extend their
activities and offerings into the MongoDB market.

This is a win/win for NoSQL and MySQL fans alike.

More About Tokutek

Tokutek is the company that productized a new and revolutionary
form of database indexing designed specifically for modern, Big
Data applications. Based on data science research on new
methods for high-performance data …

It is my pleasure to announce that Percona has acquired Tokutek
and will take over development and support for TokuDB® and
TokuMX™ as well as the revolutionary Fractal Tree® indexing
technology that enables those products to deliver improved
performance, reliability and compression for modern Big Data
applications.

At Percona we have been working with the Tokutek team since 2009,
helping to improve performance and scalability. The TokuDB
storage engine has been available for Percona Server for about a
year, so joining forces is quite a natural step for us.

Fractal Tree indexing technology—developed by years of data
science research at MIT, Stony Brook University and Rutgers
University—is the new generation data structure which, for many
workloads, leapfrogs traditional B-tree technology which was
invented in 1972 (over 40 years ago!). It is also often
superior to LSM indexing, especially for mixed workloads.

In Mo’ Data, Mo’ Problems, we explored the paradox that “Big
Data” projects pose to organizations and how Tokutek is taking an
innovative approach to solving those problems. In this post,
we’re going to talk about another hot topic in IT, “The Cloud,”
and how enterprises undertaking Cloud efforts often struggle with
idea of “problem trading.” Also, for some reason, databases are
just given a pass as traditionally “noisy neighbors” and that
there is nothing that can be done about it. Lets take a look
at why we disagree.

With the birth of the information age came a coupling of business
and IT. Increasingly strategic business projects and objectives
were reliant on information infrastructure to provide information
storage and retrieval instead of paper and filing cabinets. This
was the dawn of the database and what gave rise to companies like
Oracle, Sybase and MySQL. With the appearance of true Enterprise
Grade …

The next release of MongoDB includes the
ability to select a storage engine, the goal being that different
storage engines will have different capabilities/advantages, and
user's can select the one most beneficial to their particular
use-case. Storage engines are cool. MySQL has
offered them for quite a while. One very big difference between
the MySQL and MongoDB implementations is that in MySQL the user
gets to select a particular storage engine for each table,
whereas in MongoDB it's a choice made at server startup. You get
a single storage engine for everything on the particular mongod
instance. I see pros and cons to each decision, but that's a blog
for another day.

Content reproduced on this site is the property of the respective copyright holders.
It is not reviewed in advance by Oracle and does not necessarily represent the opinion
of Oracle or any other party.