Random insertions into or deletions from a secondary index can cause the index to become fragmented. Fragmentation means that the physical ordering of the index pages on the disk is not close to the index ordering of the records on the pages, or that there are many unused pages in the 64-page blocks that were allocated to the index.
One symptom of fragmentation is that a table takes more space than
it “should” take. How much that is exactly, is
difficult to determine. All
InnoDB data and
indexes are stored in B-trees, and their
fill factor may vary from
50% to 100%. Another symptom of fragmentation is that a table scan
such as this takes more time than it “should” take:
SELECT COUNT(*) FROM t WHERE
The preceding query requires MySQL to perform a full table scan, the slowest type of query for a large table.
To speed up index scans, you can periodically perform a
operation, which causes MySQL to rebuild the table:
As of MySQL 5.6.3, you can also use
to perform a
“null” alter operation that rebuilds the table.
FORCE option was recognized but
Another way to perform a defragmentation operation is to use mysqldump to dump the table to a text file, drop the table, and reload it from the dump file.
If the insertions into an index are always ascending and records
are deleted only from the end, the
filespace management algorithm guarantees that fragmentation in
the index does not occur.