We detected a performance regression that affects the latest released version of

flyteconsole

, the one that shipped with Flyte 1.2. More specifically we have two packages for

flyteconsole

, https://github.com/flyteorg/flyteconsole/pkgs/container/flyteconsole and https://github.com/flyteorg/flyteconsole/pkgs/container/flyteconsole-release, the latter one follows the Flyte releases. Starting with

flyteconsole:v1.2.6

and

flyteconsole-release:v1.2.0

there's a perf regression that affects large workflows (e.g. with lots of nested dynamic tasks). We'll be using https://github.com/flyteorg/flyteconsole/issues/638 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 https://github.com/flyteorg/flyteconsole/issues/638 or ping us here on the OSS slack. We expect to have a fix out shortly.

Cc @elegant-australia-91422 @brash-london-45337

@freezing-airport-6809 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

The backend should not have this problem