Since my first days in Node-RED, I wanted to develop a node that calculates the sizes of messages passing through, in other words the "throughput" of my flow. But had never time to implement it...
Until last week, when I decided to extract the logic from my node-red-contrib-msg-speed node: now I finally could reuse the entire (rolling window) logic to implement my new node-red-contrib-msg-size node
My personal usage will be monitoring the throughput of my IP camera video streams.
Like in this demo:
For those who want to experiment with it, you can install it from my Github repository from within your .node-red folder (since it hasn't been published on NPM yet!):
npm install bartbutenaers/node-red-contrib-msg-size
As always all "constructive" feedback is very welcome!!
And it would be nice to get some feedback about the following:
Is the name ok, or should I name it e.g. node-red-contrib-throughput, or perhapsnode-red-contrib-msg-throughput, or ...
Are there any other useful features that should be added?
The size of the messages is calculated using the object-sizeof package. But I'm not sure how I should interpret this limitation on their readme page:
Can anybody explain this with a simple example?
Are there any other limitations you are aware of, which I should add to my readme page (so users are aware of the limitiations)?
Do you have some nice use cases that I can add to my readme page?
P.S. Don't want to disappoint users, but this will most probably my last announcement for 2020
Have fun with it!!