Measurement of execution time of code in LabVIEW

[JohnMc19]

I think it would be a good idea to have a tool integrated into LabVIEW that would let you view the amount of time it took to run your VI.

There has been a few posts in forums asking for programmatic ways to do this, but this way would answer them all:

Clicking this would allow you to see the time it took for the last run of your VI to execute. Making it quick to see if and acute changes made to your code had made this more efficient (time-wise).

An improvement to this would be to have a sweep like feature on your block diagram that you could set up multiple markers to see the time taking for your code to reach them.

A bit like this:

These markers would be moveable and their values would update after execution.

These are just ideas, I'll be glad to hear your comments!

Regards,

[PhillipBrooks]

I don't use sequence structures in my code, so I don't know how I would use your example; but you gave me this idea:

Enhance probes by adding timestamps

Add a Probe Manager; something like the Breakpoint Manager. You would see a list of all probes and could enable timstamping (like enabling and disabling breakpoints). The Probe Manager would allow the developer to shuffle the display order and would calculate the the times between probes enabled with timestamps.

Selecting any two probes could show the time difference between them.

If a probe co-exists with a breakpoint, the timestamp should be updated before the code stops. Imagine being able to perform timing without a sequence structure, or even across VIs!

OK people, lets brainstorm a bit more and push this to the top, I want this in 2011!

EDIT

OK, I found this Idea is similar., it's similar... Jack has all the good ideas first 😞

[JohnMc19]

That is also a good idea Philip.

I think the reason why tools like these haven't been implemented in LabVIEW yet is because of its parallel programming nature!