Building on the original kSplice idea and combining
the efforts of the work done at Red Hat and SuSE,
common infrastructure is now ready to be put into the Linux 3.20
mainline kernel – Red Hat and SuSE have already committed to
using this.

I still reckon it’s freaky trickery, but heck – it works, and
it’s great for server environments that have no redundancy (I
prefer to fix that issue!) and can’t afford any downtime.

There are very interesting changes for database administrators in
these new releases, among which I would like to highlight the
fact that installer now chooses XFS as its
filesystem by default, which substitutes ext4 as the preferred
format for local data storage. Red …

With this version, the source code is now freely available under
the GPL License v2. For more details, see our blog here. Open
source pioneer Mozilla has been using TokuDB to manage its
MySQL-driven Datazilla Data cluster, an open-source system for
managing and visualizing performance data.

In the past TokuDB has been free for evaluation; the new TokuDB
Community Edition extends free use to deployed environments. With
this release Tokutek is also planning on making available a
TokuDB Enterprise Edition, which includes technical support,
initial customer onboarding services, and advanced tools for
backup and recovery.

With TokuDB v6.6 out now, I’m excited to present
one of my favorite enhancements: fast updates with TokuDB. Update
intensive applications can have their throughput limited by the
random read capacity of the storage system. The cause of the
throughput limit is the read-modify-write algorithm that MySQL
uses when processing update statements. MySQL reads a row from
the storage engine, applies the updates to it, and then writes
the new row to the storage engine. To address this throughput
limit, TokuDB uses a different update algorithm that simply
encodes the update expressions of the SQL statement into tiny
programs that are stored in an update Fractal Tree® message. This update message is
injected into the root of the Fractal Tree index. …

We wanted to take a moment to say thanks to all of our customers
and to the wider MySQL and MariaDB community. Today we announced a doubling of our customer base for
the year ending December 31, 2012. Significant milestones over
the last year included new technology and service partnerships,
several awards, rapid hiring, as well as three upgrades to
TokuDB®. We even dabbled in some MongoDB benchmarks. And to fuel
continued growth in 2013, we secured additional venture capital
funding last November.

Did You Hear? NASA Uses TokuDB for Big Data with MySQL!

To read the full press release and learn more, see here. To get started with TokuDB, …

Checkpointing — which involves periodically writing out dirty
pages from memory — is central to the design of crash recovery
for both TokuDB and InnoDB. A key issue in designing a
checkpointing system is how often to checkpoint, and TokuDB takes
a very different approach from InnoDB. How often and how much
InnoDB checkpoints is complicated, but under certain workloads it
can be relatively infrequent. In contrast, TokuDB runs a complete
checkpoint starting one minute after the last one ended.

Frequent checkpoints make for fast recovery. Once MySQL crashes,
the storage engine needs to replay the log to get back to a
correct state. The length of the log is a function of the time
since the last checkpoint for TokuDB and a more complicated
function of the workload for InnoDB. And replaying the log is
single threaded. So TokuDB recovers in minutes, and …

A key feature of our new TokuDB v6.0 release, which I have been
blogging about this week, is compression.
Compression is always on in TokuDB, and the compression we’ve
achieved in the past has been quite good. See a previous post on the 18x compression
achieved by TokuDB v5.0 on one benchmark. In our latest release,
we’ve updated the way compression works and got 50% improvement
on compression.

I decided to present numbers on the same set of data as the old
post, so see that post for experimental details.

But first, what are the changes? TokuDB compresses large blocks
of data — on the order of MB, rather than the 16KB that InnoDB
uses — …

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.