LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Slow loading VI and EXE

Highlighted

no it really was a slip on the keyboard, i meant CSV 

0 Kudos
Message 11 of 15
(159 Views)
Highlighted

thank you, i will look into this to see if if that is where the problem lies.

0 Kudos
Message 12 of 15
(157 Views)
Highlighted

I can go back to the original code which is fine, but if update it with the new mods the same thing happens. I guess my confusion is the delay is PRIOR to the actual VI being executed so there is no point in looking within the VI itself. This is why i am trying to understand the entire process from the moment you double click the exe/VI, what is being loaded, referenced etc 

 

0 Kudos
Message 13 of 15
(155 Views)
Highlighted

@gadget911 wrote:

I can go back to the original code which is fine, but if update it with the new mods the same thing happens. I guess my confusion is the delay is PRIOR to the actual VI being executed so there is no point in looking within the VI itself. This is why i am trying to understand the entire process from the moment you double click the exe/VI, what is being loaded, referenced etc 

 


Your analysis lacks reason.  The problem occurs after you modify the VI, but you believe the source of the problem is not within the VI. 

 

I suggest evaluating the difference in both the VI and EXE file sizes after the modification is made.  Some smart objects are deceptively large based on functions you may not see or have disabled.  Are you adding an XControl? You can also use Task Manager to see how much memory is used by both applications.  If there is a significant delay before the program executes, then look for the memory to increase slowly before leveling off.

 

Lastly, are you using property nodes?  You mention the change was a new table.  I've seen code where the table is initialized one cell at a time by 2 embedded for loops and one property node.

Michael Munroe, CLD, CTD, MCP
Automate 1000+ VI Search and Edit operations with Property Inspector 3.2, now with Global Exclusion™ and Persistent Selection™!
Review the top 24 Impossible with LabVIEW Categories
0 Kudos
Message 14 of 15
(135 Views)
Highlighted

@gadget911 wrote:

 I guess my confusion is the delay is PRIOR to the actual VI being executed so there is no point in looking within the VI itself.


Every edit will cause a recompile, so it is likely that the problem is there. What is your vi complexity (vi properties...memory). Do you have deeply stacked inlined hierarchies?

 

We cannot help further without seeing some actual code.


LabVIEW Champion. It all comes together in GCentral GCentral
What does "Engineering Redefined" mean??
0 Kudos
Message 15 of 15
(131 Views)