Status SQL Database after aborting

  • Resolved Ron DiLauro

    (@rdilauro)


    6 years, 3 months ago

    I have never been able to run WP-Optimize to completion doing Optimize database tables.
    So, I refresh my browser, which then puts the Optimize database tables back at the original number to optimize. In my situation is 49 tables.
    My question is than after the Optimize database tables is aborted and when you attempt to start it up again, does it recognize some of the tables were already optimized, basically like a checkpoint and continue from there. Or does it restart from the beginning.

    Can I also assume that running Optimize database tables the first time is going to take longer and that each time I run it from then on, it should be shorter in time>

    I think this tool can be valuable, but I cant tie up over 8 hours wall clock time just running and then I really dont know the end results

    The page I need help with: [log in to see the link]

Viewing 1 replies (of 1 total)
  • Plugin Author David Anderson / Team Updraft

    (@davidanderson)

    Hi Ron,

    MySQL does not have a “optimized” / “not optimized” states for tables that can be retrieved (and hence reported). WP-Optimize is ultimately a convenient front-end for the capabilities of the underlying MySQL database server, and its commands. What MySQL has is an “optimize” command (https://dev.mysql.com/doc/refman/8.0/en/optimize-table.html). When you run it, MySQL will seek to internally de-fragment its disk space usage. But it has no reported internal state to tell you what you’ll get if you do, or don’t, do it again. So, we’re limited by what’s actually under the hood, here.

    David

Viewing 1 replies (of 1 total)
  • The topic ‘Status SQL Database after aborting’ is closed to new replies.