Hot Column Addition and Deletion Part I – Performance
From 18 hours to 3 seconds!
Hot Column Addition and Deletion (HCAD) Overview
TokuDB v5.0 introduces several features that are new to the MySQL world. In this series of posts, we’re going to present some information on these features: what’s the feature, how does it work under the hood, and how do you get the most out of this feature in your MySQL setup.
Today we start with HCAD: Hot Column Addition and Deletion. Many users have had the experience of loading a bunch of data into a table and associated indexes, only to find that adding some columns or removing them would be useful. An
alter table X add column Y int default 0;
or the like takes a long time — hours or more — during which time the table is write locked, meaning no insertions/deletions/updates and no queries on the new column until the alter table is done.
Mark Callaghan points out that changing the row format in InnoDB is a “significant project”, so it looked like slow alter tables were going to be a challenge for MySQL for the foreseeable future. Slow alter tables is a reason for the inability of MySQL to scale to large tables.
TokuDB v5.0 changes all that with the introduction of HCAD. You can add or delete columns from an existing table with minimal downtime — just the time for MySQL itself to close and reopen the table. The total downtime is seconds to minutes.
Here we present an example of HCAD in action. See this page for details of the experiment. Drum roll…
mysql> alter table ontime add column totalTime int default 0; Query OK, 0 rows affected (3.33 sec)
mysql> alter table ontime add column totalTime int default 0; Query OK, 122225386 rows affected (17 hours 44 min 40.85 sec)
That’s 19,000x faster! Goodbye long downtimes.
As a note, the “0 rows affected” for TokuDB means that the column addition work happens in the background. All queries on the table, however, will see the new column as soon as the alter table returns, in this case after 3.33 sec.
We’re psyched about being able to provide this feature to our users. In the next post, we’ll take a look at how TokuDB is able to achieve HCAD. Finally, we’ll present a how-to on getting the most out of HCAD.
Click here for Part II.