-
Notifications
You must be signed in to change notification settings - Fork 128
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
Optionionally allow clustermq workers to cache the results #531
Comments
It would be super nice to use ZeroMQ to write the results back to the head node and write to the cache in parallel, but I am not sure exactly how. After the issues mention in mschubert/clustermq#99 get sorted out, |
Using the |
From #532, this issue is now solved for |
@kendonB, you called it in #425 (comment).
As with the
future
backend, we can activate the existingcaching
argument for theclustermq
andclustermq_staged
backends: i.e.This enhancement could make a major difference in the tools at my workplace, and I consider it the highest priority issue for
drake
right now. cc @huizhang-lilly.The text was updated successfully, but these errors were encountered: