all my windows installations work with this configuration:
you can make a configuration backup
and import this file in a new Mango installation without the history-values,
If you want the history-values, make a backup from the noSQL-db
To import this backup in the new system check the help via ?
If you have a new system and want only import a few data-sources, you can export this inside the old ui-system via xml:
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 :)
I also had problems with our gateway to the server. Look at the story
It is very helpful if you activate all internal data points in the data source "Mango Internal" and make a dashboard to watch them. Only then you have an overview of what leads to which problem.
The cron-job function can also help to distribute the load evenly. Not all updates (data source and ptp) at the same minute of the hour ...
So, for our 32000 data points, 268 data sources and 10 ptps, syncing history every 5 to 15 minutes, setting max 5 GB RAM I think this hardware is the minimum:
If you add some webclients you can overload the system very quick, but it's only a gateway.
The ideal computer is still to be developed. You enter your problems and they never come out.
Ok, I invest some time, deactivate all percistent TCP publishers (ptp), start again at 10:00 with only 3 and found this after one hour:
One ptp sync all the data, finished and then it is repeating that message in the log-file and stop the history-sync. The real time sync is working.
The next ptp stop at 11:00, the last stop at 11:30, same message in the log-file.
Another thing I found:
One ptp is starting and sync more than 1 Million records in 3m20s, all ok:
The next sync, same ptp, 8650 records and 4m15s?:
Thanks for the help!