made DB 1MB LARGER after optimizing InnoTables too. Negative saving!

  • size of the database
    BEFORE optimization 74.806 MB
    AFTER optimization 75.806 MB
    SAVINGS THIS TIME -1023.824 KB
    TOTAL SAVINGS SINCE THE FIRST RUN -1023.824 KB

    i opted to also optimize innotables as these are majority of what there is in my site. So after I ran optimization, DB grows in size!

    Additionally, i did not set it to delete post meta orphans only expired transients, but it got rid of orphans anyway, not sure it is a good thing as no idea what is included in these orphans. might be tags i will be using soon and not wishing to get rid of. Should have asked me first!

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

    (@cageehv)

    TekGirlyMama,

    Next time just contact me before posting this kind of stuff, okay?

    Thanks!

    Rolf

    Plugin Contributor cageehv

    (@cageehv)

    1) optimizing the database doesn’t mean shrinking the size will make it faster… for InnoDB, reorganizing makes it faster (maybe bigger but faster)
    Optimizing means: improve the performance but not per definition means making it smaller.

    2) it won’t delete orphans if you don’t check that option

    Rolf

Viewing 2 replies - 1 through 2 (of 2 total)
  • The topic ‘made DB 1MB LARGER after optimizing InnoTables too. Negative saving!’ is closed to new replies.