DB size after optimization is larger

  • Resolved v1venkatrao

    (@v1venkatrao)


    9 years, 1 month ago

    Running WP-Optimize 2.1.1. My DB size as reported by WP-Optimize, before optimizing was 10.6 MB. As a backup, I exported by DB, and the resultant SQL file was 5.7 MB. Ran the optimization, which cleaned up quite a bit. But now, WP-Optimize reports the size of the DB as 11.2 MB, larger than the original size. However, when I export the DB, the resultant SQL file is now much smaller, at 1.9 MB, which is what I would expect.

    Why is WP-Optimize reporting the DB size to be larger after optimization?

    Thanks and regards,
    — venkat

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Contributor DNutbourne

    (@dnutbourne)

    9 years, 1 month ago

    Hi Venkat,

    Apologies for the delay. Do your WordPress tables share a database with any external or non-WordPress tables?

    Thread Starter v1venkatrao

    (@v1venkatrao)

    9 years, 1 month ago

    In MySQL, there are two other databases besides this WordPress database. One of the two databases is for another WordPress installation, and the other is for a Joomla installation. All three databases have different names/users and unique table name prefixes. I do not know if this is what you asked.

    But in any case, the database and WordPress installation are running just fine!

    Thanks,
    — venkat

    Plugin Contributor DNutbourne

    (@dnutbourne)

    9 years ago

    Hi Venkat,

    It is possible that there is a bug in how the plugin is reporting the size of the database. I will pass this on to our developers for investigation.

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

The topic ‘DB size after optimization is larger’ is closed to new replies.