| This Document is not yet Rated |
Improving TestStand Deployment Utility Performance when Deploying VIs Using a Version of LabVIEW Released after the Current TestStand Version
Primary Software:
Primary Software Version: 2010
Primary Software Fixed Version: N/A
Secondary Software: LabVIEW Development Systems>>LabVIEW Base Development System
Problem: I am building a distribution using the TestStand Deployment Utility and received the following warning in the Status Log:
Loading distribution VIs. This operation can take up to five minutes, during which aborting is not supported. Refer to the National Instruments Web Site at ni.com/info and enter Info Code 'TSDULabVIEWPerformance' for information about how you can compile distribution VIs, which could improve load time.How can I address this warning and improve the time required to build the distribution?
Solution: When creating a distribution containing LabVIEW components, the TestStand Deployment Utility can exhibit decreased performance if the active version of LabVIEW was released later than your active TestStand version. In this case, LabVIEW must recompile the LabVIEW components of the TestStand Deployment Utility each time they are loaded, which increases the load time.
In TestStand 2014 and later, TestStand will automatically create a copy of the LabVIEW components the first time the new version of LabVIEW is launched. You may see a message explaining that the TestStand Distribution VIs are being mass compiled. Once this process is complete, you will see improved loading times during deployment builds.
If you are using a version of TestStand between TestStand 2010 and TestStand 2013, you can prevent this recompile operation by manually creating a precompiled copy of these LabVIEW components. The steps below describe this process.
TestStand 2010 SP1 and Later
- Close the TestStand Deployment Utility.
- Browse to the <TestStand>\Components\Tools\Deployment Utility\TestStand - Build VI Distribution directory.
Note: If a folder already exists which corresponds to the active LabVIEW version, this procedure will not improve performance, since in this case the TestStand Deployment Utility components are already compiled in your LabVIEW version
- Copy the folder with the highest version number to a writable location, such as the windows desktop.
- In the folder properties, remove the Read-Only flag from all files within the new folder.
- Rename the new folder to the active LabVIEW version, using the format "
<major version>.0" (for example, use "12.0" for LabVIEW 2012)
- Use the active LabVIEW version to mass compile the files within the folder. Before compiling, ensure that the Include warnings for read-only VIs option is enabled. If any warnings appear when the compile is complete, verify that all files have been set as not read only.
- Once the files are compiled, place the new folder in the <TestStand>\Components\Tools\Deployment Utility\TestStand - Build VI Distribution directory.
- Launch the deployment utility and rebuild the deployment.
TestStand 2010
- Close the TestStand Deployment Utility.
- Browse to the <TestStand>\Components\Tools\Deployment Utility\TestStand - Build VI Distribution directory.
Note: If a LLB already exists which corresponds to the active LabVIEW version, this procedure will not improve performance, since in this case the TestStand Deployment Utility components are already compiled in your LabVIEW version
- Copy the following files to a writable location, such as the windows desktop.
- TestStand - LabVIEW 10.0 VIs.llb
- TestStand - LabVIEW 10.0 SD.llb
- TestStand - LabVIEW 10.0 SD for PPL.llb
- TestStand - LabVIEW 10.0 PPL.llb
- In the folder properties, remove the Read-Only flag from all files within the new folder.
- Replace the version text ("10.0") in the file names with the active LabVIEW version, using the format <major version>.<minor version> (for example, use "12.0" for LabVIEW 2012)
- Use the active LabVIEW version to mass compile the files within the folder. Before compiling, ensure that the Include warnings for read-only VIs option is enabled. If any warnings appear when the compile is complete, verify that all files have been set as not read only.
- Once the files are compiled, place the new folder in the <TestStand>\Components\Tools\Deployment Utility\TestStand - Build VI Distribution directory.
- Launch the deployment utility and rebuild the deployment.
Consider using this procedure to create a folder for each installed version of LabVIEW on your machine that released after the current TestStand version. You do not need a different copy of the LLBs or folder for SP1 releases of LabVIEW. Ensure that the correct version of LabVIEW is active after you complete all steps by closing all instances of LabVIEW, then launch the version of LabVIEW that you want to be the active version.
05/02/2011
Last Updated: 10/11/2014
Document ID: 5L1CRCXU
