Measuring CVI code Build execution time

[BKOCH1]

Is there a way to measure the time it takes to build your code (compile/dll creation) and execution? I'm looking at trying to find the difference to perform the build between PC hardware platforms (Core 2 Duo vs Core i3/i5/i7 vs AMD CPUs). Yes, i'm sure the time is really small, but in a high volume environment where every second counts, we're trying to find ways to make things faster.

[Guillaume Dargaud]

You can do a small script using the 'compile' command provided by NI
(https://www.ni.com/docs/en-US/bundle/labwindows-cvi/page/cvi/usermanual/cmdlineinterface.htm).
Example of minimalist batch:
date
compile Project.prj
date

Or use cygwin and the much better 'time' pre-command.
--
Guillaume Dargaud
http://www.gdargaud.net/

[RobertoBozzolo]

The link provided by Guillaume is not working here: I suppose he is pointing you to some resource available on the online help too: search in Using LabWindows/CVI >> Managing Projects >> Building a Project >> Using the Command Line Interface (or look here ).

With reference to execution time, given that you are in a high volume environment you may benefit from the Execution Profiler Tollkit, which is a non-free add on for CVI. Some informations on the toolkit here. You may see an example of how this toolkit can be used in NickB contribution to this discussion.