Add clustermq-based staged scheduling #452
Merged
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.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Despite the inefficiencies of staged scheduling, I do not want the perfect to be the enemy of the good. For now (until mschubert/clustermq#23 is solved) this PR's new
make(parallelism = "clustermq_staged")
functionality is an attractive option in many use cases. Overhead is so much lower than in thefuture
/batchtools
backends. In fact, jobs are so agile thatdrake
needs to use checksums to wait for custom file targets to arrive over the network.cc @kendonB, @mschubert
Related GitHub issues
Checklist
drake
's code of conduct, and I agree to follow its rules.testthat
unit tests totests/testthat
to confirm that any new features or functionality work correctly.devtools::check()