TokuMX 1.0: MongoDB with transactions, compression, MVCC, clustering indexes

#1

Post by ddorian43 » Wed, Jun 19, 2013, 8:51 PM UTC

TokuMX 1.0: MongoDB with transactions, compression, MVCC, clustering indexes
tokutek.com

Re: TokuMX 1.0: MongoDB with transactions, compression, MVCC, clustering indexes

#2

Post by ekyo777 » Wed, Jun 19, 2013, 10:21 PM UTC

I'll experiment with this a bit to see for myself but I would really appreciate a list of downsides of using this over mongo; if anything else than there may be less people supporting it.

Re: TokuMX 1.0: MongoDB with transactions, compression, MVCC, clustering indexes

#3

Post by anonymous1983 » Wed, Jun 19, 2013, 10:25 PM UTC

Here are a few questions:

1. Is this a drop in replacement if I'm on Mongo 2.4? 2. If I want to migrate back to Mongodb from TokuMX, what needs to be done? 3. How quickly does TokuMX integrate improvements from MongoDB? 4. Is anyone using this in their production deployment?

Re: TokuMX 1.0: MongoDB with transactions, compression, MVCC, clustering indexes

#4

Post by kbd » Wed, Jun 19, 2013, 10:33 PM UTC

I'd love to hear any opinions the RethinkDB guys have about this.

Re: TokuMX 1.0: MongoDB with transactions, compression, MVCC, clustering indexes

#5

Post by leif » Wed, Jun 19, 2013, 10:38 PM UTC

anonymous1983 wrote: post #3

Here are a few questions: 1. Is this a drop in replacement if I'm on Mongo 2.4? 2. If I want to migrate back to Mongodb from TokuMX, what needs to be done? 3. How quickly does TokuMX integrate improvements from MongoDB? 4. Is anyone using this in their production deployment?

1. Yep 2. Dump and reload to get between mongodb and TokuMX. The storage systems and replication systems are incompatible

Re: TokuMX 1.0: MongoDB with transactions, compression, MVCC, clustering indexes

#6

Post by leif » Wed, Jun 19, 2013, 10:39 PM UTC

anonymous1983 wrote: post #3

Here are a few questions: 1. Is this a drop in replacement if I'm on Mongo 2.4? 2. If I want to migrate back to Mongodb from TokuMX, what needs to be done? 3. How quickly does TokuMX integrate improvements from MongoDB? 4. Is anyone using this in their production deployment?

3. We support 2.2 but we've back ported some things from 2.4 (like hash-based sharding) pretty easily, I think we'll be able to keep up 4. Nope, it just came out today.

Re: TokuMX 1.0: MongoDB with transactions, compression, MVCC, clustering indexes

#7

Post by leif » Wed, Jun 19, 2013, 10:41 PM UTC

ekyo777 wrote: post #2

I'll experiment with this a bit to see for myself but I would really appreciate a list of downsides of using this over mongo; if anything else than there may be less people supporting it.

The simplest list is this: no full text search, geo indexes, or background indexing yet.

Re: TokuMX 1.0: MongoDB with transactions, compression, MVCC, clustering indexes

#8

Post by ggoodale » Wed, Jun 19, 2013, 11:04 PM UTC

leif wrote: post #7

ekyo777 wrote: post #2

I'll experiment with this a bit to see for myself but I would really appreciate a list of downsides of using this over mongo; if anything else than there may be less people supporting it.

The simplest list is this: no full text search, geo indexes, or background indexing yet.

Is there a feature roadmap somewhere detailing what order these and other features will be added (actual schedule is great too!)?

Re: TokuMX 1.0: MongoDB with transactions, compression, MVCC, clustering indexes

#9

Post by ggoodale » Wed, Jun 19, 2013, 11:06 PM UTC

What's the storage multiplier for TokuMX vs. straight mongodb? Will my total size on disk go up or down?

Re: TokuMX 1.0: MongoDB with transactions, compression, MVCC, clustering indexes

#10

Post by portmanteaufu » Wed, Jun 19, 2013, 11:13 PM UTC

ggoodale wrote: post #9

What's the storage multiplier for TokuMX vs. straight mongodb? Will my total size on disk go up or down?

If I've understood their marketing material correctly, it should go down a fair amount thanks to extensive use of compression.