Hi all, I was taking another look at Mango after playing with it a while back. An upcoming project calls for some historian/SCADA work with thick/thinclient HMI's and a supervisory "booth" so a cost effective web-based server solution is being investigated. Tag count won't be over 350 but 2 of the pieces of equipment need certain sensors to be logged 1/s with and charted up live. So I threw a little something together with the VM I'm working on as my data source to populate some garbage data.
Here's my issue. Using the watchlist function I made a few windows to sort of simulate thin clients and then played with the chart update functions. Going under 5/s caused a "connectivity lost, restoring connection" warning. This would eventually spread to the other open windows and then "resolve" itself. But, while I'm getting this warning and the data points are XXXX'd out, I'm still seeing data updating and the charts updating... Is this a bug? It eventually resolves if I refresh the screen.
Upping the virtual machine to 3 cores and memory to 6GB got my windows to "resolve" faster, but the dropping error continues even though my CPU isn't maxed out and I have plenty of memory overhead (I see folks are running this on a pi, I can't see how with my test). I see this as a problem unless I'm somehow pulling and/or charting these points wrong (data source polled at 1/s, points logged as "when point value changes", . The logs show no record of a datasource losing connection, I have zero warnings or errors in the logs for the time of this test.
My typical use may see as many as 3 of these charts per screen on 2-3 screens when . user is looking closely at a sensor. Now this is with the watchlist, not a custom page, so maybe there is something more intensive about using the watchlist? I've read folks doing ms logging on here so maybe I'm missing something?
Anyway, I'd like to know before I go further into developing a project on this.