topic Re: local vs property node in LabVIEW

local vs property node

James_R — Tue, 07 Feb 2006 22:59:41 GMT

what is the difference between local variables and property nodes concerning best practices and performance ??

Thanks

James

Re: local vs property node

Darren — Tue, 07 Feb 2006 23:07:43 GMT

If possible, you always want to pass data to/from your front panel controls/indicators with wires. If this won't suffice (parallel loops, e.g.), then you will want to use locals. Try to avoid using the "Value" property unless you must write to your controls/indicators in a subVI. The "Value" property is very slow compared to locals due to threading issues associated with property nodes.

Hope this helps,

-D

Re: local vs property node

altenbach — Wed, 26 Nov 2025 01:48:17 GMT

Since you compare the two in one sentence, you must mean "Value property nodes". 😉

As Darren said, property nodes are expensive. Check out my speed comparison VI in this old thread:

https://forums.ni.com/t5/LabVIEW/local-variable-vs-property-node-gt-value/m-p/292605#M153611

(Of course if you need to write to a signaling value property in order to fire an event, a local variable won't work. You need the property node.)

Re: local vs property node

Travis_M. — Wed, 26 Nov 2025 01:48:35 GMT

Hello all,

To take it one step further, the speed hit comes from the fact that these items run in the UI thread along with all of your other user interface actions (speed), and copies are always made of the data (performance AND speed)! Check out the "LabVIEW Performance and Memory Management" tutorial -- while a little old its concepts are still dead on and it does a great job of explaining the details of these issues. If you need to pass data from/to parallel loops or sub-VIs consider putting the data in some sort of container (like a single element queue), and passing the container around.

Hope this adds just a little more insight!

Message Edited by Travis M. on 02-08-2006 02:21 PM

Re: local vs property node

Rajmohan — Wed, 04 Jan 2012 06:43:53 GMT

Really good Thread thanks

Re: local vs property node

vinod00 — Mon, 03 Dec 2012 10:22:20 GMT

Hello travis could you please pour in some more information on Property node concept and whn can it be best used?? Thanks in advance.

Re: local vs property node

Pappion — Fri, 15 Apr 2016 18:20:38 GMT

Most of the threads address time penalities writing values, not reading them.

In a new app I am reading the propert value of "STOP", as the node has an error cluster input.

That extra input helps with Data Flow paradigm.

Also I can "OR" the nodes error cluster output and "STOP" to a loop termination.

So what's the cost compared to encalsuplating "STOP" in a sequence or case structure?

Re: local vs property node

RavensFan — Fri, 15 Apr 2016 18:29:33 GMT

You can test it yourself. Oviously the property node is far worse.

Re: local vs property node

altenbach — Fri, 15 Apr 2016 20:44:11 GMT

@Pappion wrote:
Most of the threads address time penalities writing values, not reading them.

Your use of a property node also precludes the use of latch action, which is the typical mechanical action of a stop button. What does the button do? What is the rest of the code architecture?

We cannot really tell without seeing the entire diagram.

If this is a toplevel stop to end the program, I would eliminate it anyway and use an event structure for the panel close event. It is not normal or intuitive to close an program with a special stop button in some poorly defined panel location, but everybody knows the meaning of the [X] in the upper right. You can always discard the event and handle special shutdown code. You could for example enqueue the stop command at the opposite end in that event case.

You can do that in a small parallel loop that just sits there, but enqueues an exit command if the user tries to close the panel.

Re: local vs property node

Pappion — Fri, 15 Apr 2016 21:14:38 GMT

They are Test Methods for IP. So no, I can not share the APP.

The Event X close suggestion is useful. I will have to try it some time. Right now, I have no need for it.

I want to avoid using the ABORT button, and do error processing, hence the queue redirection to Exit State.

Anyway I did do my own testing, and feel like I'm goofing off....

Re: local vs property node

altenbach — Fri, 15 Apr 2016 21:57:11 GMT

I guess you see the point. 😉

Having a conditional terminal inside a FOR loop also costs something of course.

You can double the speed of all the fast loops by just disabling debugging.

Still, if you don't do it in a tight loop, it does not matter too much ....