# Nested Paths Not Allowed (Perspective) **URL:** \ **Category:** Ignition\ **Created:** [January 13, 2022, 5:10pm UTC](https://forum.inductiveautomation.com/t/nested-paths-not-allowed-perspective/54987 "2022-01-13T17:10:27Z")\ **Posts on this page:** 1\ **Showing post:** 12
**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:** [February 25, 2025, 7:04pm UTC](https://forum.inductiveautomation.com/t/nested-paths-not-allowed-perspective/54987/12 "2025-02-25T19:04:42Z")
> [@Isaiah\_Clemons](#): > > but you are saying that their is no performance difference between `tag()` and `runScript()`? Both have performance problems. In some cases, `tag()` can be much worse. > [@Isaiah\_Clemons](#): > > creating custom properties with indirect tag bindings and then using those properties in the expression binding syntax? That's almost verbatim what I wrote above. > [@Isaiah\_Clemons](#): > > explain a little more It's complicated. I've written a great deal on this and related topics. Start here: > [@Automation Professionals' Integration Toolkit Module](https://forum.inductiveautomation.com/t/automation-professionals-integration-toolkit-module/74934/68): > > I don't know all the details of tag()'s problems, but I suspect there are two key contributors: tag() startup tries to supply a proper initial value, with a 1-second timeout, on startup everywhere it is used. Use a hundred tag() calls in the bindings on a Vision template or window and you can block your UI for up to a hundred seconds, looks like. Not sure how Perspective's parallelism fits here, but you'll either tie up a thread for a hundred seconds, or tie up a hundred threads from the Per… Try [these next](https://forum.inductiveautomation.com/search?q=%40pturmel%20tag()%20indirect%20order%3Alatest). --- _[View the full topic](https://forum.inductiveautomation.com/t/nested-paths-not-allowed-perspective/54987)._