Problems with DB size after update

  • Resolved uccom

    (@uccom)


    5 years, 4 months ago

    After update to 4.0.12 my DB is growing so fast.
    Tables with so many records:
    – wp_actionscheduler_actions
    – wp_actionscheduler_logs (now size iz 5,5MB = 30% off full DB size!)
    All logs from aioseo group.

    In wp_actionscheduler_logs so many records like:
    “action started via WP Cron”
    “action complete via WP Cron”
    “action created”
    Rows are created – 3 per second.

    In wp_actionscheduler_actions so many
    “aioseo_image_sitemap_scan”
    “action_scheduler/migration_hook”
    “aioseo_admin_notifications_update”
    How I can stop this?

    P.s: After update I did not run the setup wizard and I using old sitemap module. Because I don’t want overwrite the previous settings, titles and etc.

    • This topic was modified 5 years, 4 months ago by uccom.
Viewing 12 replies - 1 through 12 (of 12 total)
  • Plugin Author arnaudbroes

    (@arnaudbroes)

    5 years, 4 months ago

    Hey @uccom,

    The next update, which is going out next week, should improve this significantly.

    The plugin will periodically clean up the actionscheduler_logs table in addition to the actionscheduler_actions one which we are already cleaning up.

    We’ve also significantly limited the number of CRON jobs that we schedule, so you should also see a big improvement there.

    After you’ve updated, can you wait for a few days and then give us some feedback?

    – Arnaud

    JayBee

    (@jbennett360)

    5 years, 4 months ago

    Same issue here.

    Will the new version clean up the mass amounts of DB entries? Or will we have to do this ourselves?

    • This reply was modified 5 years, 4 months ago by JayBee.
    Plugin Author arnaudbroes

    (@arnaudbroes)

    5 years, 4 months ago

    @jbennett360 it should clean it up. If all goes well, the update should be rolled out tomorrow. Give us a heads up in case the issue still isn’t resolved for you. You want to wait a few days because the cleanup action only runs periodically.

    JayBee

    (@jbennett360)

    5 years, 4 months ago

    @arnaudbroes Updated this morning. Will give it a few days and then check where it’s at.

    Plugin Author arnaudbroes

    (@arnaudbroes)

    5 years, 4 months ago

    @jbennett360 great! If you want to, you can actually force the CRON job to run earlier by going to the Pending actions in the Scheduled Actions menu under Tools. It’s called “aioseo_cleanup_action_scheduler”.

    JayBee

    (@jbennett360)

    5 years, 4 months ago

    @arnaudbroes I’ve done this. Pressed run. Says it executed, but the DB is still huge.

    43,926 rows
    4.1mb
    24.6kb overhead

    Plugin Author arnaudbroes

    (@arnaudbroes)

    5 years, 4 months ago

    Hmm, interesting. Would you mind reaching out to me directly here – https://aioseo.com/contact/. You can click the “Submit a Form” button and ask for me specifically. I’d love to take a look and see what’s going on.

    – Arnaud

    JayBee

    (@jbennett360)

    5 years, 4 months ago

    @arnaudbroes I’ve manually emptied that table in PHPMyAdmin. ‘_actionscheduler_logs’

    Will see if it grows again over the next few days.

    Scheduled Actions now shows

    Action Scheduler migration in progress. The list of scheduled actions may be incomplete.

    Edit: Scheduler migration complete. Table has 4 entries in PHPmyAdmin. Will see if this builds up again.

    • This reply was modified 5 years, 4 months ago by JayBee.
    • This reply was modified 5 years, 4 months ago by JayBee.
    • This reply was modified 5 years, 4 months ago by JayBee.
    Plugin Author arnaudbroes

    (@arnaudbroes)

    5 years, 4 months ago

    Sounds good!

    Those notices you saw is because Action Scheduler itself has a few entries in those tables that always are there. I don’t know exactly why, but if you delete them, Action Scheduler will regenerate them. Doesn’t cause any harm though.

    JayBee

    (@jbennett360)

    5 years, 4 months ago

    @arnaudbroes

    Fair enough. Will see how it goes. 🙂

    JayBee

    (@jbennett360)

    5 years, 4 months ago

    @arnaudbroes

    This looks to be sorted now I think?

    141 Entries – 36KB

    Does this sound about right for 7 days?

    Plugin Author arnaudbroes

    (@arnaudbroes)

    5 years, 4 months ago

    @jbennett360 Yes, that sounds about right. 🙂

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

The topic ‘Problems with DB size after update’ is closed to new replies.