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

Run Scheduler #389

Open
hardbyte opened this issue Jun 27, 2019 · 0 comments
Open

Run Scheduler #389

hardbyte opened this issue Jun 27, 2019 · 0 comments

Comments

@hardbyte
Copy link
Collaborator

When a run is created a task is added to the celery queue to chunk the similarity scoring work into multiple tasks - which are added to the same celery queue.

There is no scheduling, so a tiny job that will take <1s can be queued for hours behind a large one. A different extreme is across multiple large jobs there might be so many chunks that they don't fit in the celery queue.

One idea is to introduce a new coarse layer of chunking and apply a (fair) scheduler so all active runs get a chance to run. Interested to expand on that, or consider other approaches.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant