Clean a huge database

  • Hello ??

    We have a very big database, thousands of tables and a few hundreds of gigabytes in size, it’s time for a cleanup and this plugin looks like the best options!

    But, I am concerned with the load. I am testing the plugin now on a much smaller staging site, and for example on the setting page all the tables are displayed, this can cause a timeout on our live server. And after we start the optimization, I am not sure what will happen with all this tables to work on ..

    Any recommendation on how to handle our situation ?

    If not, i have a suggestion :
    We are using wordpress multisite, so all tables have the site ID number after the prefix (like wp_32_options for site ID = 32). How can we modify the plugin to only clean the tables that ARE checked in the settings AND modify the code to display only the tables from site ID = X to site ID = Y.

    This way, we can display in the setting a reduced number of tables, for example only 10 sites (and avoid a timeout)–> check all –> clean only this 10 sites. And do this several time with the next 10 sites to clean the whole database.
    No need to use the scheduler feature.

    Thank you for your help!

Viewing 3 replies - 1 through 3 (of 3 total)
  • Thread Starter louisblancho

    (@louisblancho)

    Any suggestion ? ??

    Thank you!

    Thread Starter louisblancho

    (@louisblancho)

    Still nothing ? ??

    Juniper

    (@juniper-webcraft)

    Loop:
    1) Freeze N sites temporarily for “scheduled maintenance”.
    2) Back up the table group for each site to keep Murphy’s Law at bay.
    3) Copy those same table groups to an empty workspace database.
    4) Run the optimization routine on the workspace tables.
    5) Copy the optimized tables back to the live database to overwrite the originals.
    6) Check the websites for errors.
    7) Unfreeze those websites.
    8) Empty the workspace database ready for the next batch.

Viewing 3 replies - 1 through 3 (of 3 total)
  • The topic ‘Clean a huge database’ is closed to new replies.