MySQL 5.5 Reference Manual :: 7 Optimization :: 7.2 Optimizing SELECT and Other Statements :: 7.2.24 Speed of DELETE Statements
Section Navigation [Toggle]
- 7.2 Optimizing SELECT and Other Statements
- 7.2.1 Optimizing Queries with EXPLAIN
- 7.2.2 Estimating Query Performance
- 7.2.3 Speed of SELECT Queries
- 7.2.4 WHERE Clause Optimization
- 7.2.5 Range Optimization
- 7.2.6 Index Merge Optimization
- 7.2.7 Condition Pushdown Optimization
- 7.2.8 Index Condition Pushdown Optimization
- 7.2.9 IS NULL Optimization
- 7.2.10 LEFT JOIN and RIGHT JOIN Optimization
- 7.2.11 Nested-Loop Join Algorithms
- 7.2.12 Nested Join Optimization
- 7.2.13 Outer Join Simplification
- 7.2.14 ORDER BY Optimization
- 7.2.15 GROUP BY Optimization
- 7.2.16 DISTINCT Optimization
- 7.2.17 Optimizing IN/=ANY Subqueries
- 7.2.18 LIMIT Optimization
- 7.2.19 Using optimizer_switch to Control the Optimizer
- 7.2.20 How to Avoid Table Scans
- 7.2.21 INFORMATION_SCHEMA Optimization
- 7.2.22 Speed of INSERT Statements
- 7.2.23 Speed of UPDATE Statements
- 7.2.24 Speed of DELETE Statements
- 7.2.25 Other Optimization Tips
The time required to delete individual rows is exactly
proportional to the number of indexes. To delete rows more
quickly, you can increase the size of the key cache by
increasing the key_buffer_size
system variable. See Section 7.5.3, “Tuning Server Parameters”.
To delete all rows from a table, TRUNCATE TABLE
is faster than
than tbl_nameDELETE FROM
. Truncate
operations are not transaction-safe; an error occurs when
attempting one in the course of an active transaction or active
table lock. See Section 12.2.11, “tbl_nameTRUNCATE TABLE Syntax”.
User Comments
Add your own comment.