Bug #18618
open
Reusing workflows/steps is too slow
Added by Ward Vandewege almost 3 years ago.
Updated 10 months ago.
Release relationship:
Auto
Description
Arvados takes too long to figure out if a workflow or step has already been run and can be reused.
A user reported that it can take ~1 minute for that determination to be made.
- Description updated (diff)
- Subject changed from It takes too long for job reuse cache hits to be returned to Reusing workflows/steps is too slow
They could try increasing the number of submit threads, eg --thread-count=4
IMO we should close this as NEEDSINFO. I doubt we're going to be able to take action on this without more information about where the slowness was (a-c-r, API server, whatever) and what the workflow looked like. And I'm guessing there's no way to get that information now.
- Target version set to Future
Also available in: Atom
PDF
Updated by 
Updated by 
Updated by