Context Storage transition from memory to persistent stores in Node-RED

Node-RED utilizes a Context API to manage state across node, flow, and global scopes. By default, this data is stored in local memory, providing high-speed access for asynchronous message flows.

When transitioning to persistent storage—such as file-based or Redis stores via settings.js—the system introduces I/O overhead for every read and write operation. In environments with high-frequency message flows and concurrent requests, this shift from memory-resident data to external I/O can impact overall throughput.

There is a need to determine the performance boundary where the reliability of persistent state outweighs the latency introduced by I/O operations during concurrent execution.

• What is the measurable latency impact on message throughput when switching from memory to persistent context storage under concurrent load?
• Are there configuration strategies to mitigate I/O blocking without reverting to volatile memory?