Thanks, It seems got fixed in 1.27.3
1 Like
not fixed for me - 100 % overload on VPS with big scenarios.
As far as I understood was the issue that the frontend gets slow. So, @lightcom, you are saying that the backend has a very high CPU load and then the frontend (UI) gets slow because of it? When does that happen? Normally, the backend has nothing to do at all, as everything runs in the browser. Only when a workflow gets executed/tested should the backend get something to do.
I’ve noticed that working with a smaller number of nodes significantly speeds up processes. I wonder if there’s a way to freeze about 90% of the nodes we’re not currently using to optimize UI performance.
Just a thought: perhaps adding a toggle button on the right of a sticky note to freeze or unfreeze nodes within its boundary could be a solution.
or build a feature such I can manually rebuild after I finish my edits.
I am suffering from the same. And in my case, I can’t split it into smaller workflows 
That sucks. @igcorreia you should be able to use execute workflow node to break apart any workflow. You can take any set of linear nodes and split them out easily. It would accept the input and return the output of the last node.
One of our staff FE engineers will be starting soon on improving the canvas and improving performance overall.
(Update: he started today)
One thing I notice was that it gets worse when we pin a response that is big. For example if we use an http request to an AI image generator with 4 images in the base64 format. That can be up to 10mg. If we pin that response and try to work the ui drags.
2 Likes
What’s most consistent and noticeable for me is that as I’m building and testing a workflow, any node that returns a lot of data will make the whole workflow editor drag, especially if I want to open that node or a node adjacent to it which results in n8n trying to load all that data for me to see.
I also noticed that the more fields in the schema, the more the schema drags. Like, two massive text fields have basically no performance effect, but thousands of small fields can crash my browser if I try to view the node.
The result is that I almost always have to test workflows with only a subset of data and constantly save to avoid clicking on the wrong thing and crashing my browser.
This is on n8n cloud, using chrome on a computer with 64GB RAM and an i7 8-core processor for the record.
Once n8n starts dragging on a big workflow I save my work, close the tab entirely, and re-open it. Refreshing it doesn’t help.
Hi @Giovanni_Segar,
Apologies for the delay in improving canvas performance for larger workflows. The good news is we’re about to release an alpha version of the completely rewritten canvas component, likely next week. You’ll have the option to try it out and switch back to the old version if any issues arise. If possible, please share your feedback to help us address any inconsistencies. Thanks in advance!
3 Likes
@C7s Exciting! I spend upwards of 2 hours every day in n8n so any improvement in performance would be very welcome.
1 Like
Hi. Any news about the new canvas?
1 Like
Indeed there is!
2 Likes