EmergencyEMERGENCY? Get 24/7 Help Now!

What is MySQL Partitioning?

 | July 27, 2017 |  Posted In: Insight for DBAs, MySQL, MySQL 101

MySQL Partitioning

In this blog, we’ll quickly look at MySQL partitioning. Partitioning is a way in which a database (MySQL in this case) splits its actual data down into separate tables, but still get treated as a single table by the SQL layer. When partitioning, it’s a good idea to find a natural partition key. You want […]

Read More

Why a Partitioned Collection Cannot Be Sharded

 | June 27, 2014 |  Posted In: Tokutek, TokuView

In TokuMX 1.5, we introduced partitioned collections for non-sharded clusters. That is, one can have a partitioned collection in a replica set, but one cannot shard a partitioned collection. In this post, I explain why. As I mentioned here, partitioned collections are useful for time-series data where we would like to keep a rolling period […]

Read More

Best Practices for Partitioned Collections and Tables in TokuDB and TokuMX

 | June 13, 2014 |  Posted In: Tokutek, TokuView

In my last post, I gave a technical explanation of the performance characteristics of partitioned collections in TokuMX 1.5 (which is right around the corner) and partitioned tables in relational databases. Given those performance characteristics, in this post, I will present some best practices when using this feature in TokuMX or TokuDB. Note that these […]

Read More

Understanding the Performance Characteristics of Partitioned Collections

 | June 10, 2014 |  Posted In: Tokutek, TokuView

In TokuMX 1.5 that is right around the corner, the big feature will be partitioned collections. This feature is similar to partitioned tables in Oracle, MySQL, SQL Server, and Postgres. A question many have is “why should I use partitioned tables?” In short, it’s complicated. The answer depends on your workload, your schema, and your […]

Read More

The Difference Between TokuMX Partitioning and Sharding

 | June 4, 2014 |  Posted In: Tokutek, TokuView

In my last post, I described a new feature in TokuMX 1.5—partitioned collections—that’s aimed at making it easier and faster to work with time series data. Feedback from that post made me realize that some users may not immediately understand the differences between partitioning a collection and sharding a collection. In this post, I hope […]

Read More

Benchmarking single-row insert performance on Amazon EC2

 | May 16, 2012 |  Posted In: Benchmarks, Cloud and MySQL, Cloud and NoSQL, Insight for DBAs, MySQL

I have been working for a customer benchmarking insert performance on Amazon EC2, and I have some interesting results that I wanted to share. I used a nice and effective tool iiBench which has been developed by Tokutek. Though the “1 billion row insert challenge” for which this tool was originally built is long over, […]

Read More

Never Settle for a “B”

 | May 24, 2011 |  Posted In: Tokutek, TokuView

OldSQL DBs based on B-trees have some well-known problems and workarounds. TokuDB is a NewSQL storage engines based on Fractal Tree indexing, so the natural question is how InnoDB practice translates into TokuDB. This post gives a quick overview. Enjoy! FAQ Q: How do I tune TokuDB? A: You don’t! TokuDB has almost no parameters […]

Read More

MySQL Partitioning: A Flow Chart

 | March 11, 2011 |  Posted In: Tokutek, TokuView

In Part 1, and Part 2 of this series, I presented some thoughts on partitioning. I heard some great feedback on why people use partitioning. Here, I present a flow chart that summarizes what I’ve learned. In summary: with TokuDB in the picture there’s almost no reason to use partitioning. Or I should say, there […]

Read More