As for Network tag, we now have data collected from five slave stations to the master station through the Remote Tag Provider (Gateway Network), and then the master station transmits to the cloud through MQTT. Each slave station has about 5000 tag points, and the polling frequency is 1 second each time. Then we developed the corresponding scada page on the master site using the Perspective. When we opened the scada page (the tag point data was read in the way of system.tag.read, not directly bound), the page would become very jammed, and the communication bandwidth between the master and slave site was occupied very high. Even if the scada page is closed, I would like to ask why the use of the Remote Tag Provider to configure the tag point keeps occupying bandwidth. Is there a problem with our structure? How should we optimize?
That's most certainly going to cause issues.
Why not do a binding to the tag in the remote tag provider?