Honestly even without nested embeded views it takes way to long.
We tried to make a warehouse with a whole bunch of instances, but it just took so long and idk why.
I made a custom module (which is basically the tempalte + the repeater) which is instant.
2 Likes
For Sure! My understanding of loading âWith-Parentâ was just that they will load at the same time, in other words youâll see your Motor display appear, with all of itâs nested views, at the same time. Like it is waiting for all of it to load before displaying any of it, if that makes sense.
How many instances you have?
Do you use too many pipeline in your view too? If yes change them to svg.
If you use flex in container in your embedded view change them to xy coordinate
Can you share a gif video of your loading time?
For me as I have 150 complex embedded view the performance is good.
For simpler embedded view I can up to 500.
1 Like
This post has my gif in it:
I have 35 EVs on the page with a max nest level of 4
I don't have any pipes
The symbol templates are a bit interesting... I created them as flex Views thinking that I would use flex for something later, and then embedded a coord container within it which ended up being the only component inside of the flex, with everything else inside the coord container. I've always been interested in comparing the load speed if I converted them all to coord Views instead.
In my experience it should be better if you use XY container so do it now.
And I always try to not go further than 2 level for repeating widget like this.
As I see your design it can be easily done with one level EV.
For the sake of the Object oriented design instead of using EV use CSS class Object oriented concept with python functions every where possible. So you can have a widget with one level of nesting.
For example I create a widget all in SVG and try to add different CSS binding by custom property and for event use function. So if I decide to change function I change CSS and python function.
Even I donât wrap it in a view and directly use in my parent view.
This approach you can reach more than 2000 obj easily.
2 Likes
That's all great information, I've always wondered how you managed to make your displays so performant.
I think though that the point is, you shouldn't have to be forced into designing a particular way to gain 12 secs on load time. The load times should be similar for all technologies, and if there is some under the hood reasons why some containers are less performant, and you want to avoid that by optimizing that's a choice you can make.
I think it's generally understood that deeply nested EV's will be less performant, how could they not be, but 12 seconds is a long time.
1 Like
Theyre not in Vision though, unless you are specifically talking about web tech
Not a fair comparison. Vision's bindings and change events run in the client. Minimal gateway traffic to hold things up (unless you screw up with foreground callouts). And minimal per-client load on the gateway (also unless you screw up).
Vision is fundamentally faster than Perspective. Hopefully, a future with WebAssembly changes that.
2 Likes
Even in Vision, I bet there is a hit for using a template over not using it, jut not a noticeable one, unless of course the windows are all pre-compiled before being loaded to the client. . After all IA has had years to optimize Vision even after it was a mature product and perspective is still fairly new.
Either way, I was speaking specifically about Perspective. I wouldn't expect there to be a noticeable difference between an EV loading in a Coordinate container as compared to an EV loading in a Flex Container.