Eduardo Apolinario (eapolinario)

11/08/2022, 10:43 PM
We detected a performance regression that affects the latest released version of
, the one that shipped with Flyte 1.2. More specifically we have two packages for
, and, the latter one follows the Flyte releases. Starting with
there's a perf regression that affects large workflows (e.g. with lots of nested dynamic tasks). We'll be using to track the work to fix this. The team is hard at work and we expect to land a fix for this in the next week or so. tldr: if you notice a slowdown in the graph view in flyteconsole after updating to Flyte 1.2., please report to or ping us here on the OSS slack. We expect to have a fix out shortly.

Ketan (kumare3)

11/09/2022, 2:24 AM
Cc @Rahul Mehta @Brian Tang

Rahul Mehta

11/10/2022, 2:26 PM
@Ketan (kumare3) this issue cropped up for us, but unfortunately will be difficult to roll back our console version since we updated it to pick up a fix for launch plan rendering. Are there any other known (non-console) issues with nested dynamic workflows? We were noticing some odd behavior here when running sub-workflows (tasks that normally complete in ~5m were taking >25m to complete and sometimes never terminating). Happy to take this to a different thread too

Ketan (kumare3)

11/10/2022, 3:54 PM
The backend should not have this problem
Let’s start a new thread
This is purely a rendering regression
Decoupled from The system