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

Better scheduling of jobs in case of server overloading #197

Open
casella opened this issue Feb 17, 2025 · 0 comments
Open

Better scheduling of jobs in case of server overloading #197

casella opened this issue Feb 17, 2025 · 0 comments
Assignees

Comments

@casella
Copy link
Collaborator

casella commented Feb 17, 2025

Currently, we have a number of periodic tasks that are scheduled on a regular basis. If for some reason there is some server overloading (e.g. due to heavy on-demand jobs running), these tasks keep piling up in the task queue, until it becomes unmanageable.

One simple strategy to avoid this problem at the root is that before starting a new job, we check if a previous instance of the same job is still running; if it is, we skip it. By construction, this avoids task of the same type piling up on the queue. I would recommend implementing this as a first quick step to avoid the current chronic overloading of our server pool.

Another strategy is to avoid scheduling a new job if nothing has changed at the scheduling time compared to the previous run.

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

No branches or pull requests

2 participants