# Overhead for Components not displayed or visible with Null bindings **URL:** \ **Category:** Ignition\ **Tags:** perspective\ **Created:** [June 22, 2023, 4:48pm UTC](https://forum.inductiveautomation.com/t/overhead-for-components-not-displayed-or-visible-with-null-bindings/75406 "2023-06-22T16:48:51Z")\ **Posts on this page:** 1\ **Showing post:** 9
**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:** [June 23, 2023, 12:41am UTC](https://forum.inductiveautomation.com/t/overhead-for-components-not-displayed-or-visible-with-null-bindings/75406/9 "2023-06-23T00:41:23Z")
Y'all might find the new `timeMe()` expression function helpful when examining this sort of question, and more complex ones.... > [@Automation Professionals' Integration Toolkit Module](https://forum.inductiveautomation.com/t/automation-professionals-simulation-aids-v2/74934/5): > > I have spent my holiday poking at this. Wanted to provide an efficient replacement for a common use of python transforms: Make a (Perspective) table that dynamically populates both .data and .columns from source dataset that isn't constrained to any particular structure or data types. In Vision, one can achieve this (mostly) by pre-populating the column attributes dataset with all of the possible column names your application might deliver. No such thing in Perspective. But a transform can … --- _[View the full topic](https://forum.inductiveautomation.com/t/overhead-for-components-not-displayed-or-visible-with-null-bindings/75406)._