Hey all, The latest release includes more performance enhancements to the Flow Run Graph, particularly for runs of ~5k+. Would love to hear how it’s working out for folks, good or bad. Also includes flow names prepended to sub-flow runs (e.g

my-flow / raging-platypus

)

Gnarliest graph screenshot wins

Hey Brandon -- I'm noticing today that it's slightly better at not crashing the page on flow runs with task runs of ~7k+, but not able to generate the Graph at that scale yet and causing the page in general to be sluggish still. Yesterday, those situations seemed to keep crashing the browser, so definitely seems improved. Out of curiosity, should we expect that eventually, the Graph will be able to handle task runs of that scale and beyond fluidly? Just asking, as potentially we may need to re-design some of our flows to lessen the quantity of task runs so it's more stable on the UI front, if that's not expected to be the case. Thanks!

@Owen McMahon thank you for sharing your experience! I do already know of a few more pretty obvious optimizations we can make, but we’re definitely seeing that scale of flow runs as more or less an edge case, so it starts to be about prioritization between further optimization and new features. Imo, 7k tasks sounds like there are for sure opportunities to break things up into some sub-flow runs? That might have other advantages around observability, etc. Sub flows are nice because you can expand them in the graph, or view them with their respective logs and such in isolation. I’m curious if you have a rebuttal to that though?