Hello all,
Some years ago I developped a TestStand OI based on LabVIEW, where loading and execution of sequence files is possible by simply doing a few clicks. Once the OI was running, it was only slightly changed but recompiled to each new LV version.
As the years and TS and LV versions went by, I noticed the following and the effect was getting bigger and bigger:
While starting the execution of the sequence in the OI, TS searches for Code Modules. This takes some amount of time, which increased over the years from version to version.
When having TestStand developer license activated, the LV modules are loaded quite fast (~30sec), and the execution starts as expected. With base deployment license, the process now takes up to 7 minutes for loading the modules before the correct execution of the sequence.
I did some tests by changing the deployment method of the LV modules in packed libraries and tried also the other options, but there was no positive effect noticeably. Now, the VIs are deployed as single files with removed Block Diagrams. In both license types, the modules are executed in LV Runtime Engine.
Yes, loading time in general can be reduced by investing millions of money in high performance computer hardware, but the big difference between the license types will then still be present.
Is this effect known to NI and/or to the community?
Are there some hints to minimize this annoying behavior?
Thanks for sharing your thoughts,
Peter
