Formed in 2009, the Archive Team (not to be confused with the archive.org Archive-It Team) is a rogue archivist collective dedicated to saving copies of rapidly dying or deleted websites for the sake of history and digital heritage. The group is 100% composed of volunteers and interested parties, and has expanded into a large amount of related projects for saving online and digital history.
Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.
Sign upImprove job scheduling #14
Open
Conversation
The new implementation is still decoupling the Worker and Job business logics. The difference comes from the flexibility given to the `views.Task` controller who can now schedule jobs as soon as the `_enqueue(...)` method is called.
Tests need to consume the generator otherwise it will be garbage collected and a GeneratorExit exception will be raised. It's Python smart but obscure optimizations :)
|
Please do not merge this yet, the state machine is not stable with parallelization. |
|
Waiting for #19 to be submitted, and then rebase this PR on the dev branch. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
dulacp commentedJul 19, 2018
•
edited
The new implementation is still decoupling the Worker and Job business logics. The difference comes from the flexibility given to the
views.Taskcontroller who can now schedule jobs as soon as the_enqueue(...)method is called.NB: Tests need to consume the generator otherwise it will be garbage collected and a GeneratorExit exception will be raised. It's Python smart but obscure optimizations :)
Cheers
TODO: