Coming in TokuMX v2.0 is a feature we’re calling “Fast Updates”. Fast updates permit certain update operations to bypass the read-modify-write behavior that most databases require (including MongoDB and the current release of TokuMX). In this blog I’ll cover how Fast Updates work by describing a simple schema and workload, plus I’ll measure the […]
Read moreThe biggest innovation in TokuDB v7.5 is Read Free Replication (RFR). I blogged a few days ago posting a benchmark showing how much additional throughput can be achieved on a replication slave, while at the same time lowering the read IO operations to almost zero. The official documentation on the feature is available here.
In […]
New to TokuDB® v7.5 is a feature we’re calling “Read Free Replication” (RFR). RFR allows TokuDB replication slaves to process insert, update, and delete statements with almost no read IO. As a result, the slave can easily keep up with the master (no lag) as well as brings all the read IO capacity of […]
Read moreToday we released TokuDB® v7.5, the latest version of Tokutek’s storage engine for MySQL and MariaDB.
I’ll be publishing two blogs next week to go into more details about our new “Read Free Replication”, but here are high level descriptions of the most important new features.
Read Free Replication
TokuDB replication slaves can now be configured to […]
MongoDB replication has a lot of great features including crash safety, automatic failover and parallel slave replication. Although MongoDB’s replication is impressive in many ways, TokuMX™ replication internals are purposely designed differently.
Register Now!
SPEAKER: Zardosht Kasheff, Sr. Engineer
DATE: Wednesday, June 11th
TIME: 1pm EDT/10am PDT
TokuMX is built on Fractal Tree® technology, unlike MongoDB’s B-tree structure. While […]
Over several posts, I’ve explained the differences between TokuMX replication and MongoDB replication, and why they are completely incompatible. In this (belated) post, I explain one last difference: the oplog format for operations. Specifically, TokuMX and MongoDB log updates and deletes differently.
Suppose we have a collection foo, with the following element:
Shell
rs0:PRIMARY> db.foo.find()
{ “_id” : […]
If you did not read my first blog post about Mark Callaghan’s (@markcallaghan) benchmarks as documented in his blog, Small Datum, you may want to skim through it now for a little context.
——————-
On March 11th, Mark, a former Google and now Facebook database guru, published an insertion rate benchmark comparing MySQL outfitted with the […]
A little background…
When I ventured into sales and marketing (I’m an engineer by education) I learned I would often have to interpret and simply summarize the business value that is sometimes hidden in benchmarks. Simply put, the people who approve the purchase of products like TokuDB® and TokuMX™ appreciate the executive summary.
Therefore, I plan to […]
MongoDB replication has some great features. As I discussed in my last post, MongoDB’s crash safety design is very elegant. In addition to that, MongoDB has automatic failover, parallel slave replication, and prefetch threads on secondaries. The latter, as Mark Callaghan points out, is similar to “InnoDB fake changes”, a feature that has helped […]
Read moreWe just released version 1.4.0 of TokuMX, our high-performance distribution of MongoDB. There are a lot of improvements in this version (release notes), the most of any release yet. In this series of blog posts, we describe the most interesting changes and how they’ll affect users.
Sharding in MongoDB and TokuMX does a great job […]
MySQL, InnoDB, MariaDB and MongoDB are trademarks of their respective owners. Proudly running Percona Server for MySQL. Copyright © 2006-2018 Percona LLC.
