Hi All,
I am trying to find if we can create 500 parallel flow in Nodered. Can we? Will there be any performance issue? If it is feasible, how can we maintain queue to avoid data loss?
Regards,
Shershah
Yes. At least in theory.
Depends where the flows are running and what they do...
500 computing intensive flows on a Raspberry will not work.
We don't know the queue you are talking about.
AFAIK, as node.js in single threaded, then, running 500 things in parallel will not really be in parallel...
If these 500 flows all do the same task, it may be more efficient to have a single flow that does 500 tasks, but it is pure speculation as you have not provided any detail. The devil is in the details.
We have few different kind of sensor category like environment sensoe, boom barrier, temperture capture, speed capture likewise. Now we have multiple device to capture all the parameters. Now there are two approaches:
- We can have flow for each sensor category
- or flow for each sensor
If we have different flow for each sensor then I get the benefit of managing individual sensor, onboarding new sensor and create alert if sensor server connectivity lost or reconnect
If I use flow for each category then I have to write many if else to accommodate sensor Id.
We have both kind of operation where we updating something on the server and receiving telemetry data.
Any reason you can’t create a flow per category, and use a switch node to split out each sensor (by its id) for that sensor category?
Then onboarding a new sensor is just a case of adding an entry in the switch node?
Having a flow per sensor seems overkill IMO
2 Likes
This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.
