Does call-caching triggers a new job? #7242
Unanswered
mariamnawaz1
asked this question in
Q&A
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hi,
I am using WDL and have been trying to understand how call-caching works, meaning if it triggers a new job. My understanding is that it starts a new job and then it checks if there was a same run in a previous workflow, if so, it call-caches it. Is that correct?
The reason why I am interested in this is that if I am running large number of samples(let's say 10k), and if all them run successfully (let's say 9500) but few fail (for example, because of out of memory), to which I restart the workflow with increased memory, I know it will call cache all the successful ones but would it trigger 10k new jobs and allocate time and memory to all the 10k jobs or would it only allocate resources to the ones that actually need to run (500 failed ones). I want to optimize my resource utilization, so I am really interested in understanding this.
Thank you!
Beta Was this translation helpful? Give feedback.
All reactions