Home > Default > Improving load times in Linux LabVIEW executable

Improving load times in Linux LabVIEW executable

October 11Hits:0
Advertisement
I'm looking for (simple) ways to improve the loading times in a Linux LabVIEW executable. We're using a low performance, low cost CPU board, and loading times are terrible. The CPU is capable of doing everything after the application is loaded, but takes forever to get there.
One of the problems is the size of the executable, that grows everytime you just look at it. Are there ways to create smaller executables? It runs from a Compact Flash card, which is ofcourse much slower than hard disk.
Another problem is a dynamic vi, that is started for every TCP connection that connects to the application. It takes a long time to load, and connecting too fast can even effectively hang up the system. Starting a handler task takes about half a second, up to a few seconds for the first task.
We're using the LabVIEW 7.1 runtime, system is a 300 MHz cyrix SBC, running from a Compact Flash.

Answers

Dennisvr wrote:
I'm looking for
(simple) ways to improve the loading times in a Linux LabVIEW
executable. We're using a low performance, low cost CPU board, and
loading times are terrible. The CPU is capable of doing everything
after the application is loaded, but takes forever to get there.   One
of the problems is the size of the executable, that grows everytime you
just look at it. Are there ways to create smaller executables? It runs
from a Compact Flash card, which is ofcourse much slower than hard disk.   Another
problem is a dynamic vi, that is started for every TCP connection that
connects to the application. It takes a long time to load, and
connecting too fast can even effectively hang up the system. Starting a
handler task takes about half a second, up to a few seconds for the
first task.   We're using the LabVIEW 7.1 runtime, system is a 300 MHz cyrix SBC, running from a Compact Flash.
I'm
not sure about the first part of your question. LabVIEW is highly
binary and does a lot of memory allocations before even one VI is ready
to be started. So maybe the memory manager is a problem. Another issue
is that the Macintosh like resource file format that is used by LabVIEW to store its VIs etc. results in
lots and lots of individual disk accesses with a rther random like
character inside a single file. So if you can configure the read
caching of your disk to use more memory this may significantly increase
the speed of loading LabVIEW VIs or applications.
And finally spawning VIs through VI server is a rather costly operation
especially on low resoruce systems. A VI is more like an executable in
many ways as far as resource consumption is concerned rather than a
thread. A much better way would be to avoid spawning subVIs altogether
and implement a queued TCP/IP server similar to the Date Time Server
example. It is a little extra work to work with this shift register
architecture but it will not have the issues of long load times for
every new TCP/IP connection coming in.
Rolf Kalbermatter
Message Edited by rolfk on 03-07-2006 06:33 PM
Rolf Kalbermatter
CIT Engineering Netherlands
a division of Test & Measurement Solutions

Read other 6 answers

Tags:

Related Articles

  • Improving load times in Linux LabVIEW executableOctober 11

    I'm looking for (simple) ways to improve the loading times in a Linux LabVIEW executable. We're using a low performance, low cost CPU board, and loading times are terrible. The CPU is capable of doing everything after the application is loaded, but t

  • Linux labview unable to run executableNovember 30

    I would like to run a labview executable and have been unable to do so.  The executable was built on a Windows platform using Labview 9.  I'm using a Linux box and when I try to run the executable from a terminal I receive the error message "bash:  c

  • Wine & Labview Executable​s?November 30

    Is it possible to run LabView executables under wine? Has anyone ever attempted to do this? Thanks for any information. Regards, KenKenneth.Miller wrote: Is it possible to run LabView executables under wine? Has anyone ever attempted to do this? Than

  • How can i load a VI from LABVIEW ver 6.0.1b3 to LABVIEW ver 6.1October 11

    How can i load a VI from LABVIEW ver 6.0.1b3 to LABVIEW ver 6.1......I want to load a vi but i'm getting this error: LabVIEW load error code 9:VI version (6.1) is newer than LabVIEW version (6.0.1b3) My LabVIEW ver is 6.1 Please help ......it's impor

  • Labview executable and WebserverNovember 30

    I'm having a little difficulty getting the webserver to run with a labview executable. (Labview 8.5) The problem appears to be that the webserver does not think that the vi is running (probably because it is an exectuable). The message is "Requested

  • Open VI Reference to a LabVIEW executable.October 11

    Hello, I haven't done this for a while and it's not working like expected.  I'm trying to "Open VI Reference" from executable A.exe to B.exe.  I'm trying to get a control value from B.exe in A.exe.  Can someone send me an example? Right now I'm

  • Is it possible to call a VI that is inside a LabVIEW executable from a TestStand sequence?October 11

    I have created a custom TestStand operator interface and have modified the default sequential process model to display a UUT information dialog that prompts for more information than just the UUT serial number.  This UUT information dialog is a LabVI

  • How can I run a labview executable file inside a VIOctober 11

    How can i add and run a labview executable file inside the vi and grab the output of the executable file to be used in the vi? mytestautomation.com ...unleashed the power, explore and share ideas on power supply testing nissanskyline.org ...your alte

  • How can I call a LabVIEW executable from within another LabVIEW executable?October 11

    I have a customer requirement for two LabVIEW executables. Based on their current setup, they need to run executable "A" or "B", both of which are under independent revision control. I have created a third "selection" executa

  • Control where a LabVIEW executable write it's Settings Configuration fileOctober 11

    Is there any way to control which directory a LabVIEW executable writes it's configuration settings file to? I am using version 7.1.I believe the INI file must be in the same directory as the executable. You can use the keys found in the LabVIEW.ini

Copyright (C) 2019 wisumpire.com, All Rights Reserved. webmaster#wisumpire.com 14 q. 0.784 s.