I have a project I’m basically duplicating but tweaking to have two gateways instead of one. One gateway collects the data and the other handles visualization. This works out so I’m effectively just changing the project’s tag provider to be a remote one hosted on the data collecting gateway (among other things). In this project, I tend to have a lot of dynamic components that use the tag structure to determine what needs to be shown on the component. This works fine on the original project, but this is causing really noticeable performance issues when I modify it to use a remote tag provider. Components often take 10-30s (or more) to show their structure and any useful information.
I can look at reducing the number of tag reads, but I see the same issue in the designer and the gateway - trying to browse the tag structure seems to consistently take a long time. Sometimes the designer won’t even open the tag provider properly, and it kind of gives up and reloads the tag browser window with the folders all closed so it doesn’t need to keep trying to browse the remote tag provider. The gateway can sometimes take a couple of minutes to browse a remote tag provider, yet at the same time when I test the remote server response I get successful responses in typically the 200-300ms range. I’m still in development, so I don’t even have that many tags in the remote tag provider yet (~300).
Is that response time expected? How can I improve the performance of browsing tags in a remote tag provider?