Feature request: Maybe an expandable section under work pool, that lists work queues along with "Flow run running" / "max allowed flow run in the queue" / "Total scheduled"

@Deceivious thanks for flagging. If this is still a consistent issue please file a github issue. If you could let me know approximately how long "ages" is that would be helpful.

Cleared the network log before selecting the tag

hmm in my testing the change is almost instant. Am I reading that screenshot correctly that its taking 26 seconds to show you updated data? A loom video would be very useful here if that is an option.

Yes. How many flows are we talking about pre and post filter?

admittedly not a lot. Hundreds of flow runs, tens of thousands of task runs, and hundreds of thousands of events. Toggling a tag that doesn't exist on any flow runs (so going from all the data to none) and things respond quickly like I'd expect. Does it behave any differently if you change the time span? Like is it also slow changing it from 24h to 8h or 1w?

Will test it out

I just tried this in a different workspace that has thousands of flow runs, hundreds of thousands of task runs, and millions of events. And its pretty snappy. What range are your counts?

110k flows

It would be helpful to get an idea of the counts the dashboard is showing. For the flow runs and task runs. Also, this is OSS and not cloud correct? Possibly there's something there. I don't have an oss instance with a large dataset but I'll see if I can get access to one

making a loom video - seeing how much I can actually share

understood, and thank you!

very interesting, that isn't a lot of data IMO and should be very responsive. And the fact that it loads quick on a page reload is interesting as well. Okay I'll dig into this. Thanks for answering all my questions!

🫡

Is this running over the network with a proxy or anything like that? Or are you accessing the ui on the machine its running on directly?

yes there is a proxy

Just trying to get a full picture. Would be curious if you have the same issue on the machine without hitting the network though. Just to eliminate pieces

I assume it is because my flow count is higher. so more partition/pagination to pull off?

The more flow runs you have the longer each api call related to flow runs takes to some extent. It feels fast on a page load because when the page first loads we incrementally load data and make checks to to see if flow runs exists at all and such. But when you change filters the page tries to update everything at once and requests stall out if you have a lot of data (slower api responses) and more requests stall due to the request limit of http1. What you could do to alleviate this is implement http2/3 and HTTPS for your prefect server. This would remove the bottle neck that http1 imposes which limits the browser to making 6 concurrent requests at a time. In cloud 1 cannot reproduce this issue (since no requests stall). We opened an issue to add some docks around this which you might want to follow. https://github.com/PrefectHQ/prefect/issues/10280

I've got like 30 flows running and around 30 other subflows running at any given time.

I don't have the exact details on that but that github issue is there so we can add some instructions on how to do so to our docs. You could also start a new slack thread about that and you might find someone else who has some insight on getting that set up.

Thanks .🫡

Not 100% sure. Can you look at the timing for a request that is taking a while and send me a screenshot? Curious if your requests are stalling like mine were

so 10s on the server is pretty slow too. But it also stalled for 12s. Which means it was stuck browser side before it even sent the request.