Improving Slow Startup and Execution Speed in LabVIEW Executable

Solution

There are general suggestions to improve the performance of an executable created in LabVIEW:

In the Build Specification configuration, ensure Enable Debugging is unchecked.
- Refer to How Can I Use LabVIEW to Debug a Built EXE File on My Local Host PC? to access the setting.
You can also dynamically call the components of your application following the indications provided in Dynamically Loading and Calling VIs.
You can also configure your LabVIEW environment to speed up the execution time of the executable created, refer to Optimizing Execution Speed for Built Applications.
If needed you can create an About Dialog Box for your stand-alone application.
You can also decide when to update your the front panel of your application as suggested in How to Force Update a LabVIEW Front Pane.

If a LabVIEW executable has different execution speeds in different LabVIEW versions, consider the following points:

Check whether the slower application is generating .dmp files. Refer to Error Log File Location after LabVIEW Crashes for instructions.
- .dmp files can still be created even if the LabVIEW Application Development Environment does not crash.
- To prevent the .dmp files from being written, check the .dmp file in WinDbg to find the root cause of the problem. Refer to Obtaining a WinDbg Dump File to Troubleshoot Crashes in NI Software for instructions.
If using any anti-virus software, try disabling it.
- The anti-virus software may detect the executable as "unknown" and block it's functionality.
If the executable logs data to fixed path, verify that the path exists on the target machine.