Perspective Performance - View Bindings vs Expression Tags

Ignition
1

I am using CSS-based styles for shading graphical components on Perspective Views for device UDT's based on their status (like Running or Failed). In regards to performance, I have found that bindings on Views can create overhead (especially in more complex views). So, I am considering using expression tags instead when able to help reduce the processing load in the Views, putting it into the Gateway instead. Is this a viable path to follow?

Example case of this:

  1. Component on View has an expression binding to its styles.classes prop that references multiple parts of a UDT instance.
  2. Instead of this, I would create an expression tag in the UDT that does that evaluation instead and bind that to the style.classes prop of the aforementioned component (i.e. Device.GraphicStyle)

Thanks!

2

Everything in Perspective runs in the gateway. There's no "instead". If you have many UDT instances (more than Perspective clients that would execute that expression in a view), you might increase the total workload in the gateway, because those expression tags would execute even when no client was using them.

1 Like
3

Interesting, so the client programs basically show the results of this processing? Does this mean that the performance of a client program is more dependent on both the speed of the connection to the gateway and the gateway's processing power and much less on its own processing power?

4

Yes, Perspective places significant load on the gateway--all customization of appearance and behavior runs in the gateway.

Your original surmise would be correct for Vision, not Perspective. Perhaps you should read this topic (and the links within):

1 Like