by Martin.FarachColton | Jan 28, 2011 | MySQL
Review In part one, I presented a very brief and particular view of partitioning. I covered what partitioning is, with hardly a mention of why one would use partitioning. In this post, I’ll talk about a few use cases often cited as justification for using...
by Martin.FarachColton | Jan 21, 2011 | MySQL
Why Partition a Database? Partitioning is a commonly touted method for achieving performance in MySQL and other databases. (See here, here, here and many other examples.) I started wondering where the performance from partitions comes from, and I’ve summarized...
by Morgan Tocker | Jan 5, 2011 | MySQL, Percona Events
Today we’re announcing Percona Live – a one day event to be held at the Bently Reserve on February 16th in San Francisco. Live is our way of showcasing some of the awesome work that has been going into MySQL recently – and the theme of this event...
by John.Partridge | Dec 9, 2010 | MySQL
Tokutek is pleased to announce support for MariaDB for the first time with TokuDB v4.1.1 for MariaDB v5.1.47. Our customers are choosing MariaDB more and more frequently for their most demanding database applications. We are delighted to help raise MariaDB performance...
by Martin.FarachColton | Nov 17, 2010 | MySQL
Summary B-trees suffer from fragmentation. Fragmentation causes headaches — in query performance and space used. Solutions, like dump and reload or OPTIMIZE TABLE are a pain and not always effective. Fractal trees don’t fragment. So if fragmentation is a...
by Morgan Tocker | Oct 26, 2010 | Benchmarks, Insight for Developers, MySQL
A couple of weeks ago I blogged about Sharing an auto_increment value across multiple MySQL tables. In the comments, a few people wrote in to suggest alternative ways of implementing this. I just got around to benchmarking those alternatives today across two large...
by Morgan Tocker | Oct 4, 2010 | Benchmarks, Insight for Developers, MySQL
The title is SEO bait – you can’t do it. We’ve seen a few recurring patterns trying to achieve similar – and I thought I would share with you my favorite two: Option #1: Use a table to insert into, and grab the insert_id: CREATE TABLE option1...
by Tokutek | Sep 2, 2010 | MySQL
Often, the first step in evaluating and deploying a database is to load an existing dataset into the database. In the latest version, TokuDB makes use of multi-core parallelism to speed up loading (and new index creation). Using the loader, MySQL tables using TokuDB...
by Rich.Prohaska | Aug 27, 2010 | MySQL
TokuDB has a big advantage over B-trees when trickle loading data into existing tables. However, it is possible to preprocess the data when bulk loading into empty tables or when new indexes are created. TokuDB release 4 now uses a parallel algorithm to speed up these...
by John.Partridge | Aug 19, 2010 | MySQL
Tokutek is pleased to announce immediate availability of TokuDB for MySQL, version 4.1.1. It is ideally suited for delivering fast response times for complex / high-volume Web applications that must simultaneously store and query large volumes of rapidly arriving...
by Martin.FarachColton | Aug 15, 2010 | MySQL
Tokutek is pleased to announce immediate availability of TokuDB for MySQL, version 4.1. It is designed for continuous querying and analysis of large volumes of rapidly arriving and changing data, while maintaining full ACID properties. New in TokuDB v4.1 includes...
by Zardosht.Kasheff | Aug 11, 2010 | MySQL
In posts on June 30 and July 6, I explained how implementing the commands “replace into” and “insert ignore” with TokuDB’s fractal trees data structures can be two orders of magnitude faster than implementing them with B-trees. Towards the end of each post, I hinted...
by Rich.Prohaska | Aug 3, 2010 | MySQL
In posts on June 30 and July 6, we explained how implementing the commands “replace into” and “insert ignore” with TokuDB’s fractal trees data structures can be two orders of magnitude faster than implementing them with B-trees. Towards...
by Rich.Prohaska | Jul 26, 2010 | MySQL
Tokutek tests its TokuDB Fractal Tree storage engine with multiple MySQL distributions. We make extensive use of the MySQL Sandbox in our test automation. We tweaked the regular expressions that match binary tarball names in the MySQL Sandbox so that MariaDB releases...
by Zardosht.Kasheff | Jul 21, 2010 | MySQL
In posts on June 30 and July 6, I explained how implementing the commands “replace into” and “insert ignore” with TokuDB’s fractal trees data structures can be two orders of magnitude faster than implementing them with B-trees. Towards...
by Zardosht.Kasheff | Jul 14, 2010 | MySQL
In my post on June 18th, I explained why the semantics of normal ad-hoc insertions with a primary key are expensive because they require disk seeks on large data sets. I previously explained why it would be better to use “replace into” or to use...
by Zardosht.Kasheff | Jul 6, 2010 | MySQL
In my post from three weeks ago, I explained why the semantics of normal ad-hoc insertions with a primary key are expensive because they require disk seeks on large data sets. Towards the end of the post, I claimed that it would be better to use “replace into” or...
by Justin Swanhart | Jul 5, 2010 | Insight for Developers, MySQL
I very much like the fact that MySQL allows you to embed comments into SQL statements. These comments are extremely convenient, because they are written into MySQL log files as part of the query. This includes the general log, the binary log and the slow query log....
by John.Partridge | Jul 3, 2010 | MySQL
Tokutek is pleased to announce immediate availability of TokuDB for MySQL, version 4.0. It is designed for continuous querying and analysis of large volumes of rapidly arriving and changing data, while maintaining full ACID properties. New in TokuDB v4.0 is our...
by Zardosht.Kasheff | Jun 30, 2010 | MySQL
In this post two weeks ago, I explained why the semantics of normal ad-hoc insertions with a primary key are expensive because they require disk seeks on large data sets. Towards the end of the post, I claimed that it would be better to use “replace into”...
