You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We have noticed that the performance of cron table selects by the module slows down over the course of the day until the cron table is cleared. My suspicion is that this is due to the getJobsByStatus query not specifying columns (https://github.com/magemojo/m2-ce-cron/blob/master/Model/ResourceModel/Schedule.php#L195-L199). In this case, the full table will be returned, including the text field for the schedule output.
The queries used by the cron service should remain performant, even if multiple days of jobs are in the table and if a large-ish number of jobs is running.
The text was updated successfully, but these errors were encountered:
JesKingDev
changed the title
Performance degredation as cron schedule table grows
SQL Performance degredation with cluster support enabled
Feb 26, 2023
JesKingDev
changed the title
SQL Performance degredation with cluster support enabled
SQL Performance degredation as cron_schedule grows
Feb 26, 2023
We have noticed that the performance of cron table selects by the module slows down over the course of the day until the cron table is cleared. My suspicion is that this is due to the
getJobsByStatus
query not specifying columns (https://github.com/magemojo/m2-ce-cron/blob/master/Model/ResourceModel/Schedule.php#L195-L199). In this case, the full table will be returned, including thetext
field for the schedule output.The queries used by the cron service should remain performant, even if multiple days of jobs are in the table and if a large-ish number of jobs is running.
The text was updated successfully, but these errors were encountered: