Hello,
We are experienced slow tag value loading. Attached picture shows screen immediately after its opening. It takes each time from 1 to 3 seconds to load all tags and show proper values.
The same things happens if we want to re-load tags using dropdown for example instead of open screen.
How to speed things up?
Are you binding complete UDTs or single tags?
When you bind complete UDTs, there’s a performance issue: per tag used of that UDT, the entire UDT will be loaded. So f.e. if you have 20 instances displayed, which display 10 tags each, you would expect it would download 200 values. However, if you define these in UDTs with f.e. 20 tags per UDT, you might expect that, in the worst case, it would download the entire UDT, so 400 values. But it will in fact will download 4000 values (the entire UDT for every time you use a tag).
The best sollution is to transform your templates to use tag paths: pass the tag paths on as strings, and use dynamic tag binding to get the individual values to display.
https://docs.inductiveautomation.com/display/DOC79/Indirect+Tag+Binding
If this isn’t the case for you, there’s probably a single slow component. Try deleting stuff, and see when it improves.
EDIT: forget about that, 1-3 seconds is actually quite normal for fresh pages. The solution here is probably to not close your windows, but open new windows on top. That way the tags remain cached.
To achieve this, you should check out the different navigation strategies: system.nav.openWindow instead of system.nav.swapTo.
Thank you for your answer.
We are binding UDTs as well as single memory tags. Performance is the same for both of them, which led us to believe that there is maybe something else wrong here.
Not closing windows would probably resolve problem to some extent, but in some cases we can change(reload) tags by selecting from dropdown button.
We were playing around, we put for exaple just 3 integer memory tags on screen but the performance (loading time for these 3 tags) remains the same.
What is your project’s poll rate?
We tried different polling rates, from 500 to 5000ms with no effect on performance.
