來源於:http://www.javashuo.com/article/p-tagtgwqy-k.html,侵刪,純截圖,避免吸引流量之嫌html
case1,刪除大表時,由於清理自適應hash索引佔用的內容致使的MySQL服務掛起git
![](http://static.javashuo.com/static/loading.gif)
![](http://static.javashuo.com/static/loading.gif)
來源:https://keithlan.github.io/2018/03/27/truncate_drop/ github
case2,大表的隨意Drop或者truncate致使MySQL服務的掛起spa
按照本文中的結論就是3d
MySQL5.6版本如下:使用truncate table + drop table 替代 drop tableorm
MySQL5.6版本+ : 直接使用drop tablehtm
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).
![](http://static.javashuo.com/static/loading.gif)
葉問中的解決辦法blog
![](http://static.javashuo.com/static/loading.gif)