Bug #77064 | Manual does not say anything about a known performance problem with TRUNCATE | ||
---|---|---|---|
Submitted: | 18 May 2015 8:43 | Modified: | 27 Jul 2015 12:10 |
Reporter: | Valeriy Kravchuk | Email Updates: | |
Status: | Closed | Impact on me: | |
Category: | MySQL Server: Documentation | Severity: | S3 (Non-critical) |
Version: | 5.5, 5.6 | OS: | Any |
Assigned to: | Daniel Price | CPU Architecture: | Any |
Tags: | innodb, missing manual, truncate |
[18 May 2015 8:43]
Valeriy Kravchuk
[19 May 2015 6:46]
MySQL Verification Team
Hello Valeriy, Thank you for the report. Thanks, Umesh
[27 Jul 2015 12:10]
Daniel Price
Posted by developer: The following information was added to the TRUNCATE TABLE documentation for 5.5, 5.6, and 5.7: "On a system with a large InnoDB buffer pool and innodb_adaptive_hash_index enabled, TRUNCATE TABLE operations may cause a temporary drop in system performance due to an LRU scan that occurs when removing an InnoDB table's adaptive hash index entries. The problem was addressed for DROP TABLE in MySQL 5.5.23 (Bug #13704145, Bug #64284) but remains a known issue for TRUNCATE TABLE (Bug #68184)." Thank you for the bug report.