@AristosQueue (NI) wrote:
If I want my project and my main .vi to load faster, what should I do? Stop using .lvlib?
If you want it to load faster:
4. Turn on "Separate compiled code from source file" on all your member VIs and libraries. Makes the VIs you are loading much smaller because the code segment is now in a separate database.
Sorry to revive an old thread, but I was struggling with a similar problem, and found one giant improvement:
Turn OFF "Separate compiled code". Contrary to what AristosQueue said, the "separate compiled code" option makes VIs load much more slowly, especially when you have a large class hierarchy. Knowing what I know now, it makes sense that separating compiled code would cause the VIs to load more slowly, because it needs to compile them when they are opened, and this compilation takes a long time with lots of dependent classes.
To open our project and top-level VI was taking nearly 15 minutes when we were using separated compiled code. When we turned this option off, it reduced the total load time to about 1 minute.
Of course, Separating compiled code has its benefits, especially when using source code control. So you'll need to assess the trade-off between load time and the number of dirty dots you are willing to deal with.
Another change that seemed to improve load time was to reduce the number of "dynamic dispatch" methods. When we first created our project, we defaulted to using dynamic dispatch all of the time. But in many cases, dynamic dispatch is not necessary and simply makes the compiler work harder.
Hopefully that saves someone some time.
