The issue I'm experiencing is related to the usage of remote tags at the gateway level. When I use system.tag.readBlocking at the gateway to fetch data from a remote ignition, it takes a significant amount of time, possibly more than ten seconds, to return results. However, when I use system.tag.readBlocking directly on the remote ignition, the execution time is very short, only a few milliseconds. Can you provide guidance on how to optimize this situation?
Hi xavier_lin,
To me, I can see how calling system.tag.readBlocking directly on the Gateway would be faster since you would just be reading tags directly on the system. With a remote tag provider, we have a GAN connection that is separating the two Gateways which may be problematic if you have network issues. Can you provide some more details on your current architecture? For example, what type of network is your Gateway network running on? If you head to the Diagnostics page on your Gateway (Gateway Config -> Gateway Network -> Diagnostics), and choose your remote tag provider's Gateway under "Test Remote Server Response", what is the Response Time? Also, do you see any errors in the logs when trying to read or write to the tags?
If you'd like, you can reach out to our support team to get a closer look at what might be happening with your system:
USA Toll-Free: 1-800-266-7798
International: 1-916-456-1045
Email: support@inductiveautomation.com