LabVIEW
Execution file performance is slower
Can you do something a bit more quatitative. Whatever you describe is very subjective.
All other things being equal, a built executable should run leaner, because all extra baggage has been removed (all diagrams, all unneeded front panels, all debugging code, etc). It will load faster and take less memory.
There are many possible scenarios that could explain your observations. For example if the development system is already in memory and you are low on free memory, starting an extra program will be more sluggish.
When you run the VI in the development system, it is already in memory and running does not add much. An executable first needs to load everything in memory. For a comparison, you should set the VI to run when openend and close LabVIEW completely. Now double click the VI to see how fast it starts up.
You need to compare apples and apples.
What does the program do, exactly?
@Timmar wrote:
My Pre-Start is up to 6 minutes and I currently have a "Please explain" in with the National Instruments R&D department.
My observations are that it looks like it is unpacking data into RAM, But that is just my best guess.
In what way does your post relate to the topic of this thread?
What is "Pre-Start"? Pre-What exactly? Are you talking about starting the computer, the LabVIEW development system, or a specific built executable? Unless you think this is all directly related to the original problem discussed here, I recommend you start a new thread.
How do you explain the reasoning of your wild guess? How much "data" is involved in your application?
@m3rv89 wrote:
Hi all, I am currently using NI LabVIEW 2012 and I have just buiilt an execution file.
1. I have noticed that if i run a VI, the performace is perfect as i get real time data for the first few seconds.
2. But when I run the execution file of that same VI that I have built, the first few seconds of the program does not respond. I think it has used up some time for some initialization.After awhile, everything runs normally as a usual VI. I would say there are some delay during the first 5 - 10 seconds.
3. Does the execution file takes up more memory and performance during the start up?
If you compare the time from activiating an icon on the desktop to pressing Run in the development environment you're comparing apples to oranges. When starting LV you load up the runtime and when opening the VI you compile if need be.
When activating a compiled .exe it loads up the runtime before being able to activate the code, thus it'll be a few seconds, even for small programs.
A more correct comparison would be to compare startup times of LV+VI+Run compared to compiled .exe. 😉
/Y
