# At what point does stacking expression binding functions become too much? **URL:** \ **Category:** Ignition\ **Tags:** scripting\ **Created:** [April 7, 2021, 9:52pm UTC](https://forum.inductiveautomation.com/t/at-what-point-does-stacking-expression-binding-functions-become-too-much/45367 "2021-04-07T21:52:34Z")\ **Posts on this page:** 1\ **Showing post:** 11
**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\ **Post date:** [April 8, 2021, 9:12pm UTC](https://forum.inductiveautomation.com/t/at-what-point-does-stacking-expression-binding-functions-become-too-much/45367/11 "2021-04-08T21:12:49Z")
> [@tmahaffey](#): > > What do you mean by staying away from tag() Some discussions (and rants) are easily found with my ID and "tag()" in a search. You can start with this topic, though: > [@Expression into Indirect Tag Binding](http://forum.inductiveautomation.com/t/expression-into-indirect-tag-binding/42584/7): > > Ah, but there is. It simply runs slower, because expressions built around it have to completely execute, even if only one little piece changes, and even if a given change wouldn’t yield a change in the output. Totally aside from the (fixed?) bugs in its implementation in v8.0. Gateway expression tags are the only place the tag() expression function makes sense. > [@paul-griffith](#): > > Once compiled, Jython or an expression are going to run about the same speed, or at least comparable. This would shock me. Even compiled, Jython has a lot more "going through one's [expletive] to get to one's elbow" gyrations. Including wrapping and unwrapping java objects / jython objects. Expressions blow jython out of the water. IIRC, @nminchin tested this for us, to that effect. --- _[View the full topic](https://forum.inductiveautomation.com/t/at-what-point-does-stacking-expression-binding-functions-become-too-much/45367)._