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

DatabaseScheduler is bad for a large amount of tasks? #786

Open
farahats9 opened this issue Aug 17, 2024 · 0 comments
Open

DatabaseScheduler is bad for a large amount of tasks? #786

farahats9 opened this issue Aug 17, 2024 · 0 comments

Comments

@farahats9
Copy link

Summary:

Hello, I am using celery beat to work with a large amount of future tasks in the database, It is starting to struggle when the number of tasks enabled is 100k+ (there are hundreds of thousands of disabled tasks)

The tasks do execute but after their scheduled time by a significant amount (few hours) which is not good for my use case, I tried scaling up the server it helped a little but the issue still exists and the number of tasks is going to increase over time.
Also increasing the number of workers doesn't seem to affect the issue very much.

Am I doing something wrong or is this the limit of the tool? any alternative solutions are very appreciated.

  • Celery Version: 5.3.6
  • Celery-Beat Version: 2.5.0

Exact steps to reproduce the issue:

  1. Create thousands of tasks with different schedules.
  2. Wait for the tasks to execute on time
  3. Notice they are delayed from the scheduled time.
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

1 participant