Verify – Database Optimisation Functionality

  • KARAM SIDHU

    (@iamkaramsidhu)


    2 weeks, 1 day ago

    Greetings WP-Optimize [Updraft] Team,

    I would like to verify a statement in the Database > Optimizations feature, specifically the Optimise database tables functionality. Refer image attached below:

    1] What do the Statement tables would be optimized (97) under the Optimise database tables represents in actual, do it suggest those tables requires optimization @ should be optimised OR it is just fetching the total tables in my site directory informing that optimization would be carried out on those tables?

    2] Upon the execution of Run all selected optimization with all sections checked, what is the final outcome [as part of best optimization practice] i should be seeing upon full [browser-end] page reload?

    What i experience is that, upon the accomplishment of Run all selected optimization with all sections checked, the statement changes to optimization completed, but, when i reload the site , the amount of tables would be optimised remains the same as before the execution. So, in good state operations of the plugin/site script/origin, should i be expecting the number of tables would be optimised to either reduce or zerorise?

    • This topic was modified 2 weeks, 1 day ago by KARAM SIDHU.
    • This topic was modified 2 weeks, 1 day ago by KARAM SIDHU.
    • This topic was modified 2 weeks, 1 day ago by KARAM SIDHU.
Viewing 1 replies (of 1 total)
  • Plugin Support wpmansour

    (@wpmansour)

    Thank you for your detailed query and for sharing the screenshot to provide additional clarity. Let me address your concerns regarding the Database > Optimizations feature in WP-Optimize.

    1] What does “Tables would be optimized (97)” mean?

    The number “97” represents the total number of database tables in your WordPress site. It is not an indication of how many tables specifically require optimization. Instead, it highlights that all 97 tables will be scanned during the optimization process, and only those with overhead or fragmentation will undergo actual optimization.

    This static count (97 in your case) will not reduce after the optimization process because it reflects the total tables present in your database, not just the ones needing optimization.

    2] Expected Outcome After Running “Run All Selected Optimizations”:

    After executing all selected optimizations:

    • You should see a message confirming that the optimization process was completed successfully.
    • However, upon refreshing the page, the “Tables would be optimized (97)” count will remain unchanged. This is expected behavior, as WP-Optimize recalculates and displays the total number of tables available, regardless of whether they required optimization or not.

    3] Why Doesn’t the Number of Tables Reduce to Zero?

    The number will not reduce or “zerorise” because it’s a static count of all tables in your database, not a metric indicating pending optimizations. To confirm successful optimizations:

    • Check the Tables tab within the WP-Optimize interface.
    • Look for a reduction in the “Overhead” column for individual tables (e.g., previously fragmented tables should now display 0 bytes).
    • This is a better indicator that optimization has been successfully performed.

    Best Practices for Database Optimization:

    • Take regular backups (using UpdraftPlus backup tool) before running optimizations.
    • Use the “Scheduled Cleaning” feature in the Settings tab to automate routine maintenance and ensure your database remains optimized over time.
    • Review the Table Information to verify changes and detect any future overhead build-up.

    I hope this clarifies your concerns!

Viewing 1 replies (of 1 total)
  • You must be logged in to reply to this topic.