You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi all! I'm new to Argo Workflows, and the use case I'm trying to solve with it envolves having a lot of workflows in the suspended state. The question is: how is the system performance if we have millions of suspended workflows? (close to 10M)
From my tests, suspended workflows are not actually considered suspended. Their status still shows as Running and they count towards the total active workflows (so it is subject to parallelism limits like the namespaceParallelism config). Is that correct?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
Hi all! I'm new to Argo Workflows, and the use case I'm trying to solve with it envolves having a lot of workflows in the suspended state. The question is: how is the system performance if we have millions of suspended workflows? (close to 10M)
From my tests, suspended workflows are not actually considered suspended. Their status still shows as
Runningand they count towards the total active workflows (so it is subject to parallelism limits like thenamespaceParallelismconfig). Is that correct?Any hints on that would be really appreciated.
Beta Was this translation helpful? Give feedback.
All reactions