No longer cleaning?

  • Resolved Magistar

    (@magistar)


    10 years, 11 months ago

    Have been using this awesome plugin for a while. However I feel the latest version is not working. For example I just “cleaned” a dev site where the plugin said it removed 399 revisions. Yet it saved 0 KB and the database is still 12MB.

    Could this be caused by the fact that the plugin has stopped optimizing Innodb?

    6. wp_posts InnoDB table: skipped… InnoDB 322 9.6 MB

    Note that the website has like +- 15 pages so it should be no where near 9MB of data.

    https://ww.wp.xz.cn/plugins/rvg-optimize-database/

    edit:
    Decided to test my theory and run a serverside Mysql –auto-repair –optimize –all-databases. The database is now 6.6 MB:
    wp_posts InnoDB table: skipped… InnoDB 440 3.6 M

    So the question is why did the plugin stop “optimizing” InnoDB? WordPress and Installatron installation both use InnoDB by default as far as I know.

Viewing 6 replies - 1 through 6 (of 6 total)
  • Plugin Contributor cageehv

    (@cageehv)

    10 years, 11 months ago

    Hey Magistar,

    Yes, I decided to skip InnoDB tables from optimization since sometimes InnoDB tables got bigger after optimization which freaked my users out…

    And no, InnoDB is not the default WordPress table type… It just depends on how MySQL was installed on the server… Upon installation you decide what the default table type will be.

    peace,
    Rolf

    Thread Starter Magistar

    (@magistar)

    10 years, 11 months ago

    Thanks for the heads up. I guess DirectAdmin with Mysql 5.x uses InnoDB by default.

    Is there a good reason to consider changing this to something like MyIsam (running a VPS)? I must admit that I never really dared to toy with this :).

    regards

    Plugin Contributor cageehv

    (@cageehv)

    10 years, 11 months ago

    I just like MyISAM better… Cannot give you any reasons for that 😉
    Switching is easy and fairly innocent.

    Rolf

    Thread Starter Magistar

    (@magistar)

    10 years, 6 months ago

    After some research I found out that when you do live snapshots the InnoDB are supposedly safer than MyISAM (that can get broken, whereas InnoDB should auto heal from journalling).

    I guess I would like to see an option to enable optimizating InnoDB :).

    Plugin Contributor cageehv

    (@cageehv)

    10 years, 6 months ago

    Hey Magistar,

    Your request has been scheduled for the next update (v4.0.1?)

    peace,
    Rolf

    wireB

    (@wireb)

    10 years, 3 months ago

    Revision: Please ignore this post – my mistake. All is working well.

    “Maximum number of – most recent – revisions
    to keep per post / page (null)
    (‘0’ means: delete ALL revisions)”

    In the above I had the checkbox check but did not enter in an integer. Possibly if you add a check to the box and add no number then there should be an error message upon saving the settings.

    If you do not add a number, the checkbox for deleting revisions does not keep the box checked upon a save settings.

Viewing 6 replies - 1 through 6 (of 6 total)

The topic ‘No longer cleaning?’ is closed to new replies.