Making the vi faster - read from txt or array or binary reading

Question

I prepared a vi that reads a table from txt file and find the desired values corresponding independent two variables by interpolation-attached. This via reads the txt file for each calculation. I wonder that is this process slow or enough for me. Becasue I add this via to a daq vi and I send measurement values from this via to the interpolation.vi. I acquired samples once in a sec. Or is this more convenient to read the txt once and after writing values to arrays and use these arrays as a constant (Right click array-->Data Operation-->Make current value default) in the vi? Which one is faster? And also, I wonder that instead of reading from txt file, is it a good way to convert my values in txt to binary data and read this binary values by vi? Last thing, how can I learn a vi program run-spend time?
Egemen
Attachments:
interpolation1.vi ‏20 KB
interpolation2.vi ‏29 KB
R600a_bar_P_0,1_sat_refprop_labview.txt ‏20 KB

Answer 1

nathand wrote:
newbieeng wrote:
Last thing, how can I learn a vi program run-spend time?
Reordering your words a bit... Are you asking how to measure how long it takes to run your VI?  You can do this with a sequence structure (one of the few reasonable uses for them): in the first frame put a "Tick Count" or "Get Date/Time in Seconds" function.  In the next frame put your code.  In the last frame, put the same function that you placed in the first frame.  Subtract the time value in the first frame from the value in the last frame; the difference is the time it took to run your VI in milliseconds or seconds (depending on which time function you used).
Another option is the VI Profiler, under Tools -> Performance and Memory.  Open that window, click "Start," run your code, and click "Stop."  It will report how much time it took to run your VI along with other timing information.
Thank you nathand. I am sorry for usage of wrong order. I tried your suggestion and it works great. The first vi takes 4-6 msec. And the second one takes just 0 msec because it does not calculate anything, including just constant values.
Egemen