Drop table performance

Drop table performance

Warning

This feature has been removed and its controlling variable innodb_lazy_drop_table has been deprecated from Percona Server 5.5.30-30.2. Feature has been removed because the upstream DROP TABLE implementation has been improved.

When innodb_file_per_table is set to 1, doing a DROP TABLE can take a long time on servers with a large buffer pool, even on an empty InnoDB table. This is because InnoDB has to scan through the buffer pool to purge pages that belong to the corresponding tablespace. Furthermore, no other queries can start while that scan is in progress.

This feature allows you to do “background table drop”.

Version Specific Information

System Variables

variable innodb_lazy_drop_table
Command Line:Yes
Config File:Yes
Scope:Global
Dynamic:Yes
Variable Type:BOOL
Default Value:FALSE
Range:TRUE/FALSE

When this option is ON, XtraDB optimizes that process by only marking the pages corresponding to the tablespace being deleted. It defers the actual work of evicting those pages until it needs to find some free pages in the buffer pool.

When this option is OFF, the usual behavior for dropping tables is in effect.

Download PDF Manual

Table Of Contents

This Page

Percona Server Series

Contact Us

For free technical help, visit the Percona Community Forum.
To report bugs or submit feature requests, open a JIRA ticket.
For paid support and managed or professional services, contact Percona Sales.