tokumx

According to a recent mailing list discussion [1], a new release of TokuMX is due by this fall.

Since rethink-guys are always in these threads: What is your opinion on implementing compression/tokumx?

ToKuMx is also supposed to use much less disk space, and this is something that this new release is meant to improve.

We've been using TokuMX for a while and I highly recommend others take a serious look there.

I'm nervous about what this means for TokuMX.

This blog post[1] compares TokuMX to vanilla Mongo running their (experimental) engine.

The short version is: TokuMX made some changes outside the scope of the pluggable storage system that give it the edge in some circumstances.

Ultimately I switched to TokuMX which substantially reduced my disk foot print, but I was a very happy MongoDB user.

The marketing copy still pretends that TokuMX doesn't exist, though - it's had these features and more (including transactions) for quite some time now.

If you hadn't seen it already, the TokuMX team is putting together a storage engine module designed to work with vanilla MongoDB's new pluggable storage system.

I had ~3TB before I migrated to TokuMX (same semantics, but at the time much faster indices and lower disk space requirements).

They are indeed building a pluggable storage engine, but the (very young) pluggable storage API limits the performance and feature improvements TokuMX SE is able to make.

TokuMX was really "MongoDB done right", at least up until MongoDB's integration of the WiredTiger engine.

TokuMX 2.0.0 was released 7 months ago, with the promise of MongoDB 2.6 support "shortly" (MongoDB 2.6 was released just over a year ago).

"TokuMX engineering team recently quit Tokutek " I would like to know how it happened.