Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

SQL Performance degredation as cron_schedule grows #134

Open
JesKingDev opened this issue Feb 23, 2023 · 0 comments · May be fixed by #135
Open

SQL Performance degredation as cron_schedule grows #134

JesKingDev opened this issue Feb 23, 2023 · 0 comments · May be fixed by #135

Comments

@JesKingDev
Copy link
Contributor

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.

CleanShot 2023-02-23 at 11 03 14@2x

@JesKingDev JesKingDev changed the title Performance degredation as cron schedule table grows SQL Performance degredation with cluster support enabled Feb 26, 2023
@JesKingDev JesKingDev changed the title SQL Performance degredation with cluster support enabled SQL Performance degredation as cron_schedule grows Feb 26, 2023
@JesKingDev JesKingDev linked a pull request Feb 26, 2023 that will close this issue
JesKingDev added a commit to JesKingDev/m2-ce-cron that referenced this issue Nov 16, 2024
JesKingDev added a commit to JesKingDev/m2-ce-cron that referenced this issue Nov 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant