<@ULVA73B9P> why is the prefect UI always have bee...
# ask-marvin
t
@Marvin why is the prefect UI always have been laggy? as i open a flow the graph always glitches, any thoughts?
m
thought for 47.0 seconds
Totally hear you — a glitchy/laggy graph is frustrating. A few common causes we’ve seen with the Prefect 3 UI: - Large/complex runs generate a lot of events and edges; the graph is browser-rendered and can get heavy or stuttery as it streams live updates and re-renders - Certain patterns (e.g., nested futures with distributed task runners) can confuse the graph builder - Browser/OS specifics (Edge on Linux in particular) can exacerbate memory/lag Known issues that may match what you’re seeing: - Events-heavy runs can consume a lot of memory and make the graph lag or even OOM in the browser: Events in FlowRun graph cause Out Of Memory - Graph breakage/lag with nested futures + RayTaskRunner: Broken Flow UI Graph with nested Futures and RayTaskRunner Quick things to try right now - In the run page, toggle off “Live updates” before opening the Graph tab; view it once the run stabilizes - Switch to the Timeline tab for large runs; it tends to be lighter than the Graph - Collapse/hide subflows/retries/failed edges (filters in the Graph view) to reduce on-screen elements - Try another browser (Chrome or Firefox) and disable heavy extensions; Edge on Ubuntu is called out in the OOM report above - If you’re using Ray/Dask and nesting futures (e.g., calling
.result()
inside loops of
as_completed
), consider restructuring to avoid nested futures or use a local
ConcurrentTaskRunner
while inspecting the graph - Break very large fan-outs into subflows so each graph is smaller - Update to the latest Prefect 3.x — there are ongoing fixes all the time; latest notes: 3.6.26 release notes (even if a specific UI fix isn’t listed, staying current helps) Could you share a bit more so I can narrow it down? - Prefect version (
prefect version
) and whether you’re on Cloud or self-hosted - Browser/OS - Approximate task count and whether you’re using Ray/Dask - Whether the lag happens only during live runs, or also when fully completed If you can share a small repro (or a redacted screenshot), I can map it to a known issue or file one on your behalf.