# Handling large message payloads and memory efficiency in custom Function nodes

**URL:** <https://discourse.nodered.org/t/handling-large-message-payloads-and-memory-efficiency-in-custom-function-nodes/101513>\
**Category:** General\
**Created:** [22 July 2026 16:43 UTC](https://discourse.nodered.org/t/handling-large-message-payloads-and-memory-efficiency-in-custom-function-nodes/101513 "2026-07-22T16:43:03Z")\
**Posts on this page:** 1\
**Page:** 2

<div class="post-metadata">

**Author:** ![TotallyInformation](https://sea2.discourse-cdn.com/flex026/user_avatar/discourse.nodered.org/totallyinformation/32/31_2.png) [@TotallyInformation](https://discourse.nodered.org/u/TotallyInformation)\
**Post date:** [13 August 2026 16:02 UTC](https://discourse.nodered.org/t/handling-large-message-payloads-and-memory-efficiency-in-custom-function-nodes/101513/21 "2026-08-13T16:02:45Z")

</div>

> [@herman34](#):
>
> For very heavy processing, moving it into a separate subflow or external service can keep the main Node RED event loop responsive.

While an external service would help - or creating a new custom node that creates a worker. A sub-flow would not help I don't believe since that is still working in the same node.js thread.

[Previous page](https://discourse.nodered.org/t/handling-large-message-payloads-and-memory-efficiency-in-custom-function-nodes/101513.md?page=1)