I could see this being a new feature/change to the way it works. Instead of only having a single delay task we could have many. For example if your meta point is context updating every 1s and your execution delay is 1hr after 1hr of running you will have 3600 tasks sitting around with 1 executing every second after that. Execution delays were not really designed for that though as if you were to stop mango or that data source you would lose 3600 point values in the tasks that had not yet run.
Nope, this data point does not recover by activating / deactivating it. And there is also nothing in the events log. After deactivation the screen looks as shown below, but reloading the page makes it look like the screenshot posted previously.
I agree with you but our Mango-PC on side is only a data collector and gateway via Persistent TCP Publisher to the cloudserver. The Mango-PC has no webpages to serve for end-users. This is the job for the cloud-server.
Our 268 data sources are 50% BACnet and 40% SNMP and 10% Modbus TCP/IP.
All BACnet-Devices are BACnet Building Controllers (TCP/IP), propper setup with COV etc, minimum network traffic.
The installation is running since 9 years with an other software as data collector and gateway, and now with Mango.
If I want to serve the webpages on side, then I have to install a much larger system as server and data-collector, I know.
MattFox has 127 users to serve, a complete other situation. A web server process with this size needs a lot of RAM and core-power.
The new experience with Mango was there are a lot of adjustment screws and you can watch and tune the system very fine, and you have to do it :)
My only thought is maybe some additional high priority threads may be required to help smack out the calcs.
Alternatively have two scripted datasources updating a single virtual datapoint. That way they can fire independently of each other.
These are just ideas, I'm not sure what else to suggest.
I have discovered that the system-timesyncd service is installed and runs out of the box (on the mangoGT). It's not able to sync for us with the default debian servers due to firewall restrictions. I just needed to put our local ntp servers in /etc/system/timesyncd.conf and it works fine.