Agree with @barn4k, but the UI is very common to come to a crawl with largescale operations happening live, even with tons of specs allocated.
It’s usually to do with the UI trying to store all outputs into memory to allow for “easy visualization”. And sometimes I’ve seen it when the server is overloaded and the socket cannot keep up so it lags the UI.
This is normal because you are probably loading a lot of information to your browser. This is not related to your server.
Your browser stores all the text and JSON you retrieve from the websites you are crawling, while you are testing your workflow.
An alternative is to create sub-workflows for parts of your logic.
That way you would process everything on the server, without storing data on your browser. And then make the sub-workflow return only a small set of information.
.
If my reply answers your question, please remember to mark it as a solution.