DB maintenance optimizes administrator-selected tables in the database during regular cron.php executions. For MyISAM tables, OPTIMIZE TABLE repairs a table if it has deleted or split rows, sorts table indexes, and updates table statistics. For BDB and InnoDB, OPTIMIZE rebuilds the table. Note, MySQL locks tables during the time OPTIMIZE TABLE is running.
OPTIMIZE works best on tables with large deletions (e.g. cache or watchdog), however MySQL will reuse old record positions, therefore in most setups, OPTIMIZE TABLE is unnecessary unless you just like defragmenting. The Overhead column in phpMyAdmin's database view is the most common way to determine the need of an OPTIMIZE TABLE query. It essentially shows the amount of disk space you would recover by running an optimize/defragmentation query.
Think of OPTIMIZE TABLE like defragmenting your hard drive. Sure your system will run without it, and it might even be fast, but isn't it nice to run a defrag when you can?
6.x+ PostgreSQL support: Per PostgreSQL documentation's recommendation, this module does not use the VACUUM FULL operation that locks the tables; this module can operate in parallel with normal reading and writing of PostgreSQL tables.
If you are using prefixed tables you will need to upgrade to 7.x-2.4, 8.x-1.4, 2.0.x for this module to work correctly.
Similar project: OptimizeDB.
7.x-2.x
7.x-2.x branch is released. The module has been completely rewritten in object-oriented Drupal 8 style. This is an intermediate stage for Drupal 8 module version. For Drupal 8 OOP (Object Oriented Programming) style in Drupal 7 version X Autoload module >=7.x-5.0 is required. Module functionality remains the same. People, who are OK with 7.x-1.x may continue using it. But new development is in 7.x-2.x.
8.x-1.x
Drupal 8 version of the module is available. It is a 7.x-2.x version upgraded to D8. Module functionality remains the same.
2.0.x
Drupal 9 version of the module is available. It is a 8.x-1.x patched version. We also switch to semantic versioning to ensure future 9||10 API compatibility. Module functionality remains the same.
3.0.x
Drupal ^10 version of the module.
Project information
- Project categories: Developer tools
3,346 sites report using this module- Created by deekayen on , updated
Stable releases for this project are covered by the security advisory policy.
Look for the shield icon below.
Releases
First release of the 3.1.x branch. Requires Drupal 12. Sites on Drupal 11 or earlier should stay on 3.0.x.
Development version: 3.1.x-dev updated 8 Oct 2026 at 16:42 UTC
released 8 October 2026
First stable 3.x release: Drupal 10, 11 and 12 compatibility, per-database "optimize all tables" option, fixes for multi-database sites and the logging setting, config cleanup, and the first automated tests.
Development version: 3.0.x-dev updated 8 Oct 2026 at 15:46 UTC
