You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I concern about the performance of stream sheets. For example, My plant has 300 standalone machines, each machine needs collection sensor data for (vibration/temperature/speed) of many motors and has 100 signals per machine. So if apply full plant, we have 300 x 100 = 300.000 signal/seconds.
My sheet simply just consumes from MQTT consumer and use Rest for storing in InfluxDB only.
So is streamsheets is suitable for this case?
Context
I look in deep repos and found that streamsheets is developed by Node.js. And Node.js only have 1 JS thread event-loop for handler code logic. So node.js JS thread event-loop will busy to process sheet-logic so for a same time have large signal can be slow?
Apart from the IPC implementation that allows what you describe above, Streamsheets' microservice architecture allows for horizontal scaling. Of course there is always room for improvements.
Activity
tangkhaiphuong-colpal commentedon Mar 25, 2020
After looking in deep process of streamsheets. I found
Each Stream Machine is handled by
usr/local/bin/node /streamsheets/packages/machine-core/src/ipc/MachineTask.js --owner anonSo if I have 10 stream machine. I have 10 process run independent so the it's no problem for many stream machine.
evlach commentedon Mar 25, 2020
Apart from the IPC implementation that allows what you describe above, Streamsheets' microservice architecture allows for horizontal scaling. Of course there is always room for improvements.