# Passing Row Value into a Component **URL:** \ **Category:** Ignition\ **Created:** [October 30, 2023, 3:29am UTC](https://forum.inductiveautomation.com/t/passing-row-value-into-a-component/81142 "2023-10-30T03:29:07Z")\ **Posts on this page:** 1\ **Showing post:** 20
**Author:** ![Felipe\_CRM](https://avatars.discourse-cdn.com/v4/letter/f/dfb087/32.png) [@Felipe\_CRM](https://forum.inductiveautomation.com/u/Felipe_CRM)\ **Post date:** [October 30, 2023, 8:09pm UTC](https://forum.inductiveautomation.com/t/passing-row-value-into-a-component/81142/20 "2023-10-30T20:09:34Z")
I was actually about to look up which one was more performant, I know they're technically both terrible for performance if overused but I never remember which is less bad. EDIT: Yeah, found the thread. Something about transforms adds a really nasty bottleneck to execution. Nothing that matters if your script only executes once every second, but adds up if you have multiple. > [@Tag binding or expression to read dynamic list of tags](https://forum.inductiveautomation.com/t/tag-binding-or-expression-to-read-dynamic-list-of-tags/76610/16): > > Collected some overhead stats. Added a sixth binding for comparison, and made them all trigger from a common reference. The new expression transform looks like this: nanoTime() - {value} It is notably faster than the other transforms. To make the recorder() run smoothly, I made a trigger timestamp with now({this.custom.pace}) and set pace to 200. Then I modified the transforms' first stages to look like this: asList( {this.custom.trigger}, nanoTime() )[1] The non-transform tests of run… As a bonus, with `runScript()` you'd be able to set up a polling rate naturally, whereas with the script transform, you'd have to call `now()` in the base expression since otherwise it will never refresh. --- _[View the full topic](https://forum.inductiveautomation.com/t/passing-row-value-into-a-component/81142)._