Deployment Utility hangs when placing support VIs in SupportVIs.llb

[Niek]

Hello,


I am trying to deploy a TestStand 4 workspace and a LabView 8.5 UI. Normally this takes about 5 minutes (which is quite long, I think), but when I chose to put the support vi's in a VI library instead of in a directory, then the deploying takes very long and after half an hour, it is still not finished.
I think it is hanging on adding VIs to the SupportVIs.llb, because during this half an hour the SupportVIs.llb is growing to 20 mb. And when it reached that size its size keeps changing with a few kb up and down.
After more then half an hour I abort the deploying process.
If I put the support VIs in a directory,then the directory size is also 20 mb, so it seems to be that the deployment utility is almost finished putting the support VIs in the VI library.

I am I doing something wrong? Is there a solution for this problem?


Regards,


Niek

[Niek]

I have find out the following: Putting VIs in a library does work but takes a lot time:

• If Locking of the VIs is disabled, then this will take 15 minutes (ten minutes more then putting support VIs in a directory)
  
• If Locking of the VIs is enabled, then this will take 46 minutes (!) (fourty minutes more then putting support VIs in a direcetory)
  

Why does deploying of the project takes so much time (I think 5 minutes is also a lot of time for deploying such a simple project) and why does it take more time if Locking of the VIs is enabled?


Niek


Message Edited by Niek L. on 06-26-2008 06:57 AM

[Rick_Francis]

Niek

We are doing speed optimizations on the deployment utility- would you mind if we contacted you via email to get a copy of your system as a test case?

>Why does deploying of the project takes so much time (I think 5 minutes is also a lot of time for deploying such a simple project) and why does it take more time if Locking of the >VIs is enabled?

It's hard to know if the absolute times are reasonable without knowing the details of your system.   The deployment utility must save every subVI for your systems therefore if you are using a VI from VI.lib tht contains many subVIs then it will take a long time to save all of the subVIs.   Using LLBs will always be slower than directories.  LLBs are compressed so every write must compress the data and every read must uncompress it.   Unless you have a specific reason to use an LLB I would suggest using a directory instead.

When the deployment utility Locks VIs it reloads each VI, locks the VI, and then re-saves it.  If there is a large number of VIs locking VIs could easily double the build time.  If you have several simple top level VIs that share a large number of subVIs then it isn't unreasonable that it would take three times as long.

-Rick Francis

[Niek]

Hello Rick,


You can contact me by e-mail. Can you see my e-mail address in my profile?

Niek

Message Edited by Niek L. on 06-30-2008 02:38 AM

[Rick_Francis]

Niek,

Thank you for your assistance- since you have given your permission we can get your email from the database administrator so you don't have to post it.   I've talked with our product support engineer- he will be sending you an email in the next couple of days with instructions on how to submit the source.  

-Rick Francis