by Tokutek | Mar 29, 2011 | MySQL
Running with Big Data It’s spring here in Boston, though one could hardly tell (still barely hitting 40°F). So, for those stuck indoors working out on the treadmill, or those lucky enough to do a workout outdoors, we’ve got a great podcast. Our Chief...
by Tokutek | Mar 24, 2011 | MySQL
Customers and Users Ernie Souhrada, Chief IT Architect at Jawa “With the introduction of Hot Schema Changes in TokuDB v5.0, Tokutek makes deriving value out of a large MySQL database simple, giving us the option to much more easily analyze our data and generate value...
by Tokutek | Mar 23, 2011 | MySQL
The Big Data Opportunity “What if you could analyze every transaction, capture insights from every customer interaction, and didn’t have to wait for months to get data from the field?”- McKinsey Column, Financial Times Despite this tremendous opportunity, MySQL...
by Martin.FarachColton | Mar 11, 2011 | MySQL
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...
by Tokutek | Mar 3, 2011 | MySQL
As Huey Lewis once noted, sometimes it’s “Hip To Be Square.” Apparently, occasionally, someone even pays attention to you when you are. Xconomy just featured “10 Boring Boston-Area Tech Companies That Are Actually Interesting” and we made the cut. As they note...
by Tokutek | Feb 1, 2011 | MySQL
Links to the FAQ Sections can be found here: General Information Open Source Technical Details Best Practices and Tools General Information ANY CHARACTER HERE 1. What is TokuDB? TokuDB is an ACID compliant storage engine for MySQL that is specifically designed for...
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 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 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 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 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”...
by Zardosht.Kasheff | Jun 22, 2010 | MySQL
The analysis that shows how to make deletions really fast by using clustering keys and TokuDB’s fractal tree based engine also applies to make updates really fast. (I left it out of the last post to keep the story simple). As a quick example, let’s look at...
