Contrib.social

Potential to bring in improvements or merge with OptimizeDB

Open on Drupal.org →
Created on 11 December 2023, 7 months ago
Updated 17 June 2024, 9 days ago

I'm again trying to assess a standard module suite for new and upgrading client projects, and came across this comparison of the db_maintenance and optimizedb modules.

The module "DB Maintenance" is similar to the module "OptimizeDB" but there are important differences:

1. Table Optimization is not performed by Cron, as this may disrupt the experience of site.
2. There is a cleaning table cache_form, because this table is very often grows and sometimes is large.
3. In the settings module, you can see the size of all tables in the database, there is the ability to sort by size.
4. Optimization tables is performed using Batch Api.
5. Optimization by Cron replaced by warning of the need to optimize.
6. Separate output size of the table cache_form
7. Withdraw the total size of all the tables.

NEW

8. The table listing all tables in the database have the opportunity "Checks", "Repair" and "Optimization" tables.
9. #2451863: Clear entire cache_form table at specified hour, ex: 4:00am Possible ? → Opportunity to select the amount of time to perform the Cron operations. Feature will be added soon to the stable branch.

I am by no means a database expert and don't even understand some of the benefits/detriments of a few of these key differences. But it appears OptimizeDB is the more used and potentially better supported module, and I'm wondering if it would be possible to include any improvements from this list and/or potentially merge the projects and their respective team's skillsets and time resources.

It sounds like a merge would allow a best supported project to emerge with the best options, UI, reporting, etc.

💬 Support request
Status

Active

Version

3.0

Component

Documentation

Created by

🇺🇸United States W01F

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

  • Issue created by @W01F
  • Comment 9 days ago →
    🇹🇷Turkey Orkut Murat Yılmaz

    @W01F, should we include those differences as features to db_maintenance?

  • Comment 9 days ago →
    🇺🇸United States W01F

    Hi @Orkut, I would simply recommend:

    1. Starting a discussion with the current maintainers of this module and reaching out to the OptimizeDB maintainers to discuss potentially joining forces, including:
    • Which module would be best to promote as recommended
    • Deprecating the other, possibly with an upgrade path?
  • Identify any features, code improvements, etc. that could/should be done on the identified module to take forward.
  • Update all information and docs - module pages with mentions of the other/previous modules, readmes, possibly the comparison listed above, etc.

    • Alternatively, if the discussion reveals a valid reason to maintain both modules such as different important implementation points, target users or cases, etc. - then a note to that effect explaining the differences to help guide potential users should be added to the module descriptions.

contrib.social Blog FAQ Discussions
Production build 0.69.0 2024