Support » Plugin: Optimize Database after Deleting Revisions » Database size increased after deleting revisions

  • Resolved Mike Clarke

    (@rawthey)


    I’ve been experimenting with the Optimize Database after Deleting Revisions plugin on the development version of my site before installing it on the production site. As expected the first run made a huge reduction in the size of the database but when I made another run today the size of the database actually increased slightly.

    Here’s a summary of the log with columns with all zeros removed.
    The first and third runs were manual, the second was a cron job.

    
              - - - - - Deleted - - - -  Optimised    - - - - - Database - - - - -
              revisions  trash  orphans   tables      BEFORE      AFTER     SAVINGS
    12/14/2017  3800     1      18967       57       33.906 MB  16.703 MB  17.203 MB
    12/15/2017     0     0          0       57       17.797 MB  16.625 MB 	1.172 MB  
    12/16/2017    32     0          1       57       16.641 MB  17.75 MB    -1136 KB
    
    

    I’m not particularly worried about the size increasing in the third run, just curious how it could happen.

    • This topic was modified 1 year, 4 months ago by  Mike Clarke.
    • This topic was modified 1 year, 4 months ago by  Mike Clarke.
    • This topic was modified 1 year, 4 months ago by  Mike Clarke.
Viewing 1 replies (of 1 total)
  • Plugin Author cageehv

    (@cageehv)

    Hey Mike,

    This topic has been here several times…

    It’s because you are using the InnoDB engine (I assume).

    InnoDB basically wants to increase the speed and not the size of the DB.

    (See the FAQ)

    Thanks for your feedback!

    peace,
    Rolf

    • This reply was modified 1 year, 4 months ago by  cageehv.
Viewing 1 replies (of 1 total)
  • The topic ‘Database size increased after deleting revisions’ is closed to new replies.