EmergencyEMERGENCY? Get 24/7 Help Now!

TokuMX vs. MongoDB : In-Memory Sysbench Performance

 | September 10, 2013 |  Posted In: Tokutek, TokuView

In talking to existing MongoDB users and TokuMX evaluators, I’ve often heard that the performance of MongoDB is very good as long as your working data set fits in RAM. The story continues that if your working data set grows to be larger than the RAM on your server, the built-in sharding capabilities of MongoDB […]

Read More

Announcing TokuMX v1.2: Hot Backup

 | September 5, 2013 |  Posted In: Tokutek, TokuView

We’ve been hard at work on TokuMX since it’s initial release just over 2 months ago. Today we released TokuMX v1.2 which includes Hot Backup in the Enterprise Edition. Hot Backup allows users to create a backup of a running TokuMX primary or secondary server in a replica set, with no blocking of writes for […]

Read More

TokuMX tip: Create any field name you want

 | August 15, 2013 |  Posted In: Tokutek, TokuView

A common MongoDB tip is to create short field names to save storage space. Because MongoDB does not compress its data on disk and stores field names in each document, using longer field names leads to bigger documents which leads to more storage space usage. The downside here is developers find short field names unintuitive […]

Read More

Building TokuMX and TokuDB for Production

 | August 7, 2013 |  Posted In: Tokutek, TokuView

Recently, we’ve seen a few people ask us about building TokuMX from scratch. While it’s best if you just use the binaries you can get from us (they have all the right optimizations, we’ve tested them, and we can interpret coredumps they generate), we recognize there are other reasons you might need to do a […]

Read More

Slides from Boston MongoDB User Group Meetup on 7/31/13

 | August 2, 2013 |  Posted In: Tokutek, TokuView

On Wednesday night, the Boston MongoDB User group was kind enough to have me speak about TokuMX Internals. I spoke about Fractal Tree® indexes and the technical reasons behind the benefits they provide to MongoDB applications. Although the talk mostly references TokuMX and MongoDB, all the theory applies to TokuDB and MySQL as well. My slides […]

Read More

Schema Design in MongoDB vs Schema Design in MySQL

 | August 1, 2013 |  Posted In: Insight for Developers, MongoDB, MySQL

For people used to relational databases and doing MySQL database design, using NoSQL solutions such as MongoDB brings interesting challenges. One of them is schema design: while in the relational world, normalization is a good way to start, how should we design our collections when creating a new MongoDB application? Let’s see with a simple […]

Read More

TokuMX 1.0.3: Seamless Migrations from MongoDB

 | July 23, 2013 |  Posted In: Tokutek, TokuView

Since we released TokuMX, one of the most frequent requests has been for a migration tool. TokuMX has a completely different storage format than MongoDB, which means that you have to actually move all of your data out of MongoDB and into TokuMX, you can’t just switch out the servers and use the same data. […]

Read More

Comparing MongoDB, MySQL, and TokuMX Data Layout

 | July 22, 2013 |  Posted In: Tokutek, TokuView

A lot is said about the differences in the data between MySQL and MongoDB. Things such as “MongoDB is document based”, “MySQL is relational”, “InnoDB has a clustering key”, etc.. Some may wonder how TokuDB, our MySQL storage engine, and TokuMX, our MongoDB product, fit in with these data layouts. I could not find anything […]

Read More

Why Unique Indexes are Bad

 | July 15, 2013 |  Posted In: Tokutek, TokuView

Before creating a unique index in TokuMX or TokuDB, ask yourself, “does my application really depend on the database enforcing uniqueness of this key?” If the answer is ANYTHING other than yes, do not declare the index to be unique. Why? Because unique indexes may kill your write performance. In this post, I’ll explain why. […]

Read More