Reduce flow rendering to a single flow zone
My team maintains a very large Dataiku project with 500+ flow zones. We intentionally keep this work in a single project so we can manage version control and promotion to automation nodes cleanly, without having to coordinate dependencies and changes across multiple projects.
Most of our work is done through the API, but we still need to use the Dataiku UI at times, and that is where we run into performance issues.
Because the project flow is so large, rendering it takes a long time. Even with 300+ flow zones collapsed and the Flow Display settings optimized, the Flow view can still take 30+ seconds to load.
Our expectation was that opening a specific flow zone by zoneId would allow Dataiku to render only that zone, which would be much faster since we usually work in just one zone at a time. However, even when a zoneId is specified, Dataiku still appears to call the same backend endpoint:
/dip/api/flow/recipes/get-graph-serialized
It seems like Dataiku still computes or serializes the entire project flow graph, then narrows the display to the selected zone. As a result, loading a single flow zone still takes 30+ seconds.
It would significantly improve usability for large projects if expanding or opening a flow zone could render only that zone in isolation, without first rendering the rest of the project.