Project

General

Profile

Actions
Copy link

Bug #18618

open

Reusing workflows/steps is too slow

Added by Ward Vandewege over 2 years ago. Updated about 2 months ago.

Status:
New
Priority:
Normal
Assigned To:
-
Category:
-
Target version:
Future
Story points:
-
Release:
Postponed
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.

Actions
Copy link
 #1

Updated by Ward Vandewege over 2 years ago

  • 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
Actions
Copy link
 #2

Updated by Peter Amstutz over 2 years ago

They could try increasing the number of submit threads, eg --thread-count=4

Actions
Copy link
 #4

Updated by Peter Amstutz about 1 year ago

  • Release set to 60
Actions
Copy link
 #5

Updated by Brett Smith about 1 year ago

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.

Actions
Copy link
 #6

Updated by Peter Amstutz about 2 months ago

  • Target version set to Future
Actions
Copy link

Also available in: Atom PDF