Low Loading Speed of Perspective views

I can see my Perspective views (Symbols) are loading gradually on pages when I start or change the page. (It loads one by one i can do 1 to 10 counts for that)
though my Gateway memory seems ok. I used 8 GB of Ram. and into Server grade PC.

Any other properties to check?

Lots of embedded views ? Scripts ?


see the video where i add 100 View (Symbols) of same type on a page and i can see them loading one by one.

the individual view does not have embedded view but yes is linked to lot of custom property and uses SVGs.

The problem likely comes from embedding so many views.
Try to get rid of them and put the symbols directly on the page, it's MUCH faster - I just tried with about 120 symbols and they all load at the same time in about 1 second.
Make them simple, so that it's actually doable to un-embed them, and that there aren't too many things to load at once. Then open a popup with more details when one of the symbols is clicked.

I try to stay away from embedded views in general and only use them for complex components.

You may find this useful.

1 Like

Perhaps play with the loading order as well in your template views. perhaps try setting to load with the parent instead of after. I forget the exact terminology..

Edit: the prop is loading Perspective - Embedded View - Ignition User Manual 8.1 - Ignition Documentation

I'd be interested to see a screenshot of the structure of your template view as well (the symbol) which shows all of its components in the project tree. That seems slower than I'd expect. What version are you on?

yes, it does make difference while "loading with parent", but still, it takes much time.
But this setting has to be manually changed when i drop my embedded view.
Is there possible to change it in default?

here is page Structure -> This has only embedded Templates (but in other case we have lables and images along with this Embedded views

Here is my Embedded view Template structure -> it has Custom Properties and lot bindings.

I don't think you should be binding inner properties of a property that's bound itself. Sounds like a recipe for disaster. It also makes very little sense: Either the parent property is dynamic and generates the children props, or it's fixed and the children are in charge of computing themselves.