We are doing a really deep dive into our mysql database performance and discovered some really excessive repetitive queries from ATUM. Excessive like 1200 times for each hook in 3 hours for 3600 queries. These are the hooks and the code in the schedule. There is definitely something being overdone to need to run the same query 400 times an hour.
I don't want to delete the plugin as it is useful, but there is something not right. I don't know if it is a loop or if there is something in the schedule code that can be fixed, but I need to get this worked out.
atum/check_trials
O:32:"ActionScheduler_IntervalSchedule":5:{s:22:"scheduled_timestamp";i:1681936950;s:18:"first_timestamp";i:1681501992;s:13:"*recurrence";i:86400;s:49:"ActionScheduler_IntervalSchedulestart_timestamp";i:1681936950;s:53:"ActionScheduler_IntervalScheduleinterval_in_seconds";i:86400;}
atum/update_expiring_product_props
O:32:"ActionScheduler_IntervalSchedule":5:{s:22:"scheduled_timestamp";i:1681951205;s:18:"first_timestamp";i:1681516800;s:13:"*recurrence";i:86400;s:49:"ActionScheduler_IntervalSchedulestart_timestamp";i:1681951205;s:53:"ActionScheduler_IntervalScheduleinterval_in_seconds";i:86400;}
atum/clean_up_tmp_folders
O:32:"ActionScheduler_IntervalSchedule":5:{s:22:"scheduled_timestamp";i:1682106802;s:18:"first_timestamp";i:1681501992;s:13:"*recurrence";i:604800;s:49:"ActionScheduler_IntervalSchedulestart_timestamp";i:1682106802;s:53:"ActionScheduler_IntervalScheduleinterval_in_seconds";i:604800;}