-
Notifications
You must be signed in to change notification settings - Fork 544
Nodes 2.0: Performance and usability issues caused by replacing canvas‑based node rendering with DOM elements #10831
Description
What problem are you experiencing?
The ongoing shift in Nodes 2.0 toward rendering node graphics as individual DOM elements introduces significant performance and interaction problems when working with medium or large workflows. As the number of nodes and connections increases, I experience inconsistent frame pacing with fps drops from 60+ down to below 5 regularly, delayed interaction feedback with some button presses and interactions not responding properly, and severely impacting sluggishness and reduced responsiveness during common actions such as dragging, zooming, or selecting nodes.
These issues pretty much affect the core usability of the interface. Canvas panning being smooth and having stable interaction with UI are required for building and managing complex workflows. When the interface becomes sluggish or visually unstable, it becomes impossible to navigate and use ComfyUI.
When does this problem occur?
-
When working with medium or large workflows that contain many nodes and connections
-
When dragging nodes or groups of nodes
-
When zooming or panning the workspace
-
When the workflow is running and updates such as progress bar or activity indicator on node is displayed
How often do you encounter this problem?
Multiple times per day
How much does this problem affect your workflow?
Significantly slows down my work
Current workarounds
I simply do not use Nodes 2.0 as it is not even feasible.
Ideas for solutions (Optional)
No response
Additional context
Node editors in professional tools such as Unreal Engine, Blender, Houdini, and Substance Designer rely on GPU‑accelerated scene rendering rather than DOM elements. This approach provides stable performance, predictable interaction timing, and smooth navigation even when the graph becomes large and with less impact on the GPU as workflow size increases. The current DOM‑based approach in Nodes 2.0 introduces overhead that grows quickly with workflow size, which affects both responsiveness and usability.
Video demonstrating how extreme the impact is:
msedge_NheRMvBYmW.mp4
┆Issue is synchronized with this Notion page by Unito