Innodb/XtraDB tables do benefit from being reorganized often. You can get data physically laid out in primary key order as well as get better feel for primary key and index pages and so using less space,
it is just OPTIMIZE TABLE might not be best way to do it.
If you're running Innodb Plugin on Percona Server with XtraDB you get benefit of a great new feature - ability to build indexes by sort instead of via insertion. This process can be a lot faster, especially for large indexes which would get inserts in very random order, such as indexes on UUID column or something similar. It also produces a lot better fill factor. The problem is.... OPTIMIZE TABLE for Innodb tables does not get advantage of it for whatever reason.
Lets take a look at little benchmark I done by running OPTIMIZE for a second time on a table which is some 10 times larger than amount of memory I allocated for buffer pool:
-
CREATE TABLE `a` (
-
`id` int(10) UNSIGNED NOT NULL AUTO_INCREMENT,
-
`c` char(64) DEFAULT NULL,
-
PRIMARY KEY (`id`),
-
KEY `c` (`c`)
-
) ENGINE=InnoDB AUTO_INCREMENT=12582913 DEFAULT CHARSET=latin1
-
-
mysql> SELECT * FROM a ORDER BY id LIMIT 10;
-
+----+------------------------------------------+
-
| id | c |
-
+----+------------------------------------------+
-
| 1 | 813cf02d7d65de2639014dd1fb574d4c481ecac7 |
-
| 2 | 62960f5d5d50651e5a5983dacaedfa9a73a9ee87 |
-
| 3 | cea33998792ffe28b16b9272b950102a9633439f |
-
| 4 | 8346a7afa0a0791693338d96a07a944874340a1c |
-
| 5 | b00faaa432f507a0d16d2940ca8ec36699f141c8 |
-
| 6 | 8e00926cf6c9b13dc8e0664a744b7116c5c61036 |
-
| 7 | f151fe34b66fd4d28521d5e7ccb68b0d5d81f21b |
-
| 8 | 7fceb5afa200a27b81cab45f94903ce04d6f24db |
-
| 9 | 0397562dc35b5242842d68de424aa9f0b409d60f |
-
| 10 | af8efbaef7010a1a3bfdff6609e5c233c897e1d5 |
-
+----+------------------------------------------+
-
10 rows IN SET (0.04 sec)
-
-
# This is just random SHA(1) hashes
-
-
mysql> OPTIMIZE TABLE a;
-
+--------+----------+----------+-------------------------------------------------------------------+
-
| TABLE | Op | Msg_type | Msg_text |
-
+--------+----------+----------+-------------------------------------------------------------------+
-
| test.a | OPTIMIZE | note | TABLE does NOT support OPTIMIZE, doing recreate + analyze instead |
-
| test.a | OPTIMIZE | STATUS | OK |
-
+--------+----------+----------+-------------------------------------------------------------------+
-
2 rows IN SET (3 hours 3 min 35.15 sec)
-
-
mysql> ALTER TABLE a DROP KEY c;
-
Query OK, 0 rows affected (0.46 sec)
-
Records: 0 Duplicates: 0 Warnings: 0
-
-
mysql> OPTIMIZE TABLE a;
-
+--------+----------+----------+-------------------------------------------------------------------+
-
| TABLE | Op | Msg_type | Msg_text |
-
+--------+----------+----------+-------------------------------------------------------------------+
-
| test.a | OPTIMIZE | note | TABLE does NOT support OPTIMIZE, doing recreate + analyze instead |
-
| test.a | OPTIMIZE | STATUS | OK |
-
+--------+----------+----------+-------------------------------------------------------------------+
-
2 rows IN SET (4 min 5.52 sec)
-
-
mysql> ALTER TABLE a ADD KEY(c);
-
Query OK, 0 rows affected (5 min 51.83 sec)
-
Records: 0 Duplicates: 0 Warnings: 0
That's right ! Optimizing table straight away takes over 3 hours, while dropping indexes besides primary key, optimizing table and adding them back takes about 10 minutes, which is close than 20x speed difference and more compact index in the end.
So if you're considering running OPTIMIZE on your tables consider using this trick, it is especially handy when you're running it on the Slave where it is OK table is exposed without indexes for some time.
Note though nothing stops you from using LOCK TABLES on Innodb table to ensure there is not ton of queries starting reading table with no indexes and bringing box down.
You can also use this trick for ALTER TABLE which requires table rebuild. Dropping all indexes; doing ALTER and when adding them back can be a lot faster than straight ALTER TABLE.
P.S I do not know why this was not done when support for creating index by sorting was implemented. It looks very strange to me to have this feature implemented but majority of high level commands
or tools (like mysqldump) do not get advantage of it and will use old slow method of building indexes by insertion.
Entry posted by Peter Zaitsev | 7 comments
Add to: 
| 
| 
| 
| 
PlanetMySQL Voting: Vote UP / Vote DOWN