by Dave Rosenlund | Oct 16, 2013 | MySQL
Tokutek is proud to be a sponsor of the MongoDB Boston 2013 event in Boston next Friday, October 25. The annual one-day conference is dedicated to MongoDB and is featuring all new advanced sessions this year. A few things to look forward to according to...
by Zardosht.Kasheff | Oct 11, 2013 | MySQL
Since introducing TokuMX, we’ve discussed benefits that TokuMX has for existing MongoDB applications that require no changes. In this post, I introduce an extension we’ve made to the indexing API: clustering indexes, a tool that can tremendously improve query...
by Dave Rosenlund | Sep 25, 2013 | MySQL
Save Time & Money – Do It Right The First Time SPEAKER: Tim Callaghan, VP Engineering, Tokutek DATE: Thursday, September 26th TIME: 1pm ET If you are thinking of using the leading NoSQL database in a project, learn just how easy it is to get started with...
by Tim.Callaghan | Sep 10, 2013 | MySQL
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...
by Tim.Callaghan | Sep 5, 2013 | MySQL
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...
by Zardosht.Kasheff | Aug 15, 2013 | MySQL
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...
by Leif.Walsh | Aug 7, 2013 | MySQL
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...
by Zardosht.Kasheff | Aug 2, 2013 | MySQL
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...
by Stephane Combaudon | Aug 1, 2013 | 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...
by Leif.Walsh | Jul 23, 2013 | MySQL
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...
by Zardosht.Kasheff | Jul 22, 2013 | MySQL
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,...
by Zardosht.Kasheff | Jul 15, 2013 | MySQL
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...
by Zardosht.Kasheff | Jul 9, 2013 | MySQL
In my last post, I showed what a Fractal Tree® index is at a high level. Once again, the Fractal Tree index is the data structure inside TokuMX and TokuDB, our MongoDB and MySQL products. One of its strengths is the ability to get high levels of compression on the...
by Zardosht.Kasheff | Jul 2, 2013 | MySQL
With our recent release of TokuMX 1.0, we’ve made some bold claims about how fast TokuMX can run MongoDB workloads. In this post, I want to dig into one of the big areas of improvement, write performance and reduced I/O. One of the innovations of TokuMX is that it...
by Vadim Tkachenko | Jun 25, 2013 | Cloud, MySQL
I am actually quite excited about Tokutek’s release of TokuMX. I think it is going to change the landscape of database systems and it is finally something that made me looking into NoSQL. Why is TokuMX interesting? A few reasons: It comes with transactions, and...
by Martin.FarachColton | Jun 19, 2013 | MySQL
Tokutek is known for its full-featured fast-indexing technology. MongoDB is known for its great document-based data model and ease of use. TokuMX, version 1.0, combines the best of both worlds. So what, exactly, is TokuMX? The simplest (but incomplete) answer is that...
by Peter Zaitsev | Jun 19, 2013 | MySQL
In many environments MySQL is not the only technology used to store in-process data. Quite frequently, especially with large-scale or complicated applications, we use MySQL alongside other technologies for certain tasks of reporting, caching as well as main data-store...
by Tim.Callaghan | Jun 6, 2013 | MySQL
Tokutek created the iiBench benchmark back in 2008. The point of the benchmark is to measure the performance of indexed insertions over time. It uses an extremely simple schema, one table with a sequential insertion pattern for the primary key along with three integer...
by Zardosht.Kasheff | Jun 3, 2013 | MySQL
Over several blog posts, Tim has presented performance results on large data sets of TokuMX, our MongoDB product with fractal tree indexes integrated, side by side with MongoDB. Results look good. We’ve shown improved throughput numbers on a sysbench benchmark,...
by Tim.Callaghan | May 28, 2013 | MySQL
Two months ago I posted a performance comparison running Sysbench on MongoDB versus MongoDB with Fractal Tree Indexes v0.0.2. The benchmark showed a 133% improvement in throughput. Nice, but our engineering team had an effort on our road-map for lock refinement that...
