-
Notifications
You must be signed in to change notification settings - Fork 7
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
Use component cache for NoFlo #55
Labels
Comments
So, two steps:
|
jonnor
added a commit
that referenced
this issue
Feb 3, 2016
Prerequisite for using NoFlo component cache feature Refs #55
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Takes a good bit of startup time due to being so I/O intensive.
An alternative would be to change the Processors to be long-running processes, controlled over FBP protocol. Then startup cost would only matter at worker startup, not per compute job.
The text was updated successfully, but these errors were encountered: