ENH: Add support for reduced SGEgraph on re-run #1002
Conversation
During the re-running of a workflow with SGEgraph, we can greatly reduce the dependancies by determining which nodes have completed prior to generating the submit-graph. Job numbers need to be based on job ID's not on job names. Job names are not unique. BUG: Job names must be valid bash variables.
|
@hjmjohnson - how do you know that a node upstream is not going to change it's output? so even when it looks like a node is done, it may get new inputs. specifically since at this point we are not hashing environments - libraries may change, binaries may change so upstream outputs from a node may change. or are you simply saying in the expanded graph i will eliminate any nodes that won't change right from the root of the graph? i think this is the sort of thing that should be done (as a configurable option) in the base class before jobs are executed. |
|
@satra I don't have a deep enough understanding of how nippy works. It appears that these changes are allowing my large 7000 jobs to run efficiently on our cluster. Without this, I was overloading the cluster environment with a tremendous number of jobs that only ran to determine if they needed to run, and that caused HUGE performance and cluster penalties. Regarding the configuration option: I'd be supportive of that, but I don't know how to implement it. |
There was a problem hiding this comment.
This is where we can add the config option.
3 participants
During the re-running of a workflow with SGEgraph, we can greatly
reduce the dependancies by determining which nodes have completed
prior to generating the submit-graph.
Job numbers need to be based on job ID's not on job names. Job names are not unique.
BUG: Job names must be valid bash variables.