We have an Ignition application with some (Main) Windows having many (100-300) “images”. The “images” are typically the multi-layered Template Instances where each Template itself may consists of several components (3-10), including one or more Template instances (In fewer cases, however, the “image” may just be a single built-in Ignition component).
When we developed the application in the Ignition Designer, there wasn’t any issue with the speed for loading/opening the Windows with many “images”. At worst, the Windows would be loaded/opened after 2-4 seconds of loading.
However, as we deploy our application, our clients complaint on those Windows as sometimes it might take 20-60 seconds (or even unresponsive) when they try to open those Windows. This is not only happening when our client’s PC is old (some of our client PCs are newer and more powerful, but some are not), but also when our client’s PC is new. When they open a Window without many “images” the speed of the loading is acceptable, but not so for the Windows with many “images”.
And so, we look for solution to speed up this loading.
Some of questions we have:
- How do we know how much data (kB/MB) needs to be sent to the client side per Window? Is there any way to monitor this? When we open the Task Manager, the Network Tab only shows the overall Network activity of Ignition (java.exe) over time - not individual Window. We would be happy if we can have this info for our investigation
- What are the possible reasons for this slow/unresponsive behavior? Bad network? Too much data per Window? Why when we developed the application, the speed was of no issue, but when we deploy the application, the speed becomes the issue for old and new client PCs alike?
- We realize that we use many multi-layered Template Instances for the application. We are wondering if this could be a possible reason for the slow response. Is this true? How much slower can a multi-layered Template Instance be compared to, say, single (built-in) Ignition component or single layer Template Instance (where a Template consists only (built-in) Ignition components and not another Template)
Looking forward for the response.