Solution
When working with large projects it is recommended to use PPLs to improve performance. LabVIEW packed project libraries are project libraries that package multiple files into a single file with a .lvlibp file extension. Build time is shorter if portions of the stand-alone application are in packed libraries. IN order to improve loading times, follow these general recommendations:
- Include only related VIs in a packed library. When you open a VI in a packed library, all VIs in the packed library load. If you include non-related VIs, load time increases because more VIs need more time to load.
- Check the Separate compiled code from source file setting for VIs. This can be modified by going to VI Properties >> General. LabVIEW will load source-only VIs more quickly than regular VIs, this can be done for all the files in a VI hierarchy or project.
- Some LabVIEW toolkits or extensions can affect the IDE performance. Project Providers in LabVIEW add features to the editor like pull-down menus, right-click menus in the project, toolbars, icon overlays, etc. Some features that use providers to include these features include build specs (EXE, PPL, etc.), VI Analyzer, Actor Framework, Source Code Control, etc. With LabVIEW closed, rename the following folder: LabVIEW 20xx\resource\Framework\Providers\GProviders to something like GProviders_bak. When you restart LabVIEW, all project providers will be disabled. If this fixes the performance issues, then there might be a provider that is causing the editor slowdowns. At that point, you can restore the GProviders folder, and start renaming INI files in that folder to figure out which one is problematic.
- Clear the compiled code cache.
- Mass compile the LabVIEW folder. Mass compile the project code.
- Backup LabVIEW INI file in case there is something in it causing issues.
- Uninstall add-ons from VIPM that might affect editor load time/performance. OpenGDS for example is a popular add-on from the Tools Network that slows down LabVIEW editor and project load time.
- If you have circular dependencies between libraries/classes, that could cause slow editor behavior. The Class Dependency Viewer tool can help locate circular dependencies in code: Tools - LabVIEW Craft.
- Reconsider refactoring the PPL into smaller, logically-grouped PPLs. VIs need to distributed according to their function related to the main program.
- It is recommended that you use the latest version of LabVIEW since it will include all the improvements in performance related to loading PPLs.