Node-RED runtime latency during high-volume Debug node output

Event Loop Blocking in High-Throughput Flows

Node-RED operates on a single-threaded Node.js event loop. When flows are configured to process high-frequency message bursts, the runtime may experience significant latency or reduced editor responsiveness.

A specific concern arises when the Debug node is used to monitor large payloads or rapid message streams. Because these outputs must be transmitted to the sidebar or system console, the overhead of processing these messages can compete with the execution of the primary flow logic.

There is uncertainty regarding the exact threshold where Debug node activity begins to block the event loop, particularly when combined with CPU-intensive Function nodes.

• What is the impact of Debug node output volume on the Node.js event loop latency?
• Does the memory pressure caused by high-frequency debug logging trigger garbage collection cycles that further stall flow execution?