Quelques règles sur les problèmatiques de temps de chargement des projets. Le texte est une compilation d'informations internet (Pas de moi.)
Some rules to reduce project load time. This text is a blog posts compilation. (i'm not the author). Links at the end (LAVA or NI website).
http://forums.ni.com/t5/LabVIEW/How-to-reduce-project-load-time/td-p/936487
The project is a list of the files that you included and their locations :
Any VI that is loaded will load all of its subVIs, whether the subVIs are explicitly listed in the project or not.
To improve the performance (about LV R&D, Aristos Queue) : Put all your VIs and classes into a .llb file. The .llb optimizes the contents of the file and significantly improves load speed when a block of VIs must load as one.
https://lavag.org/topic/14174-extremely-long-load-time-with-lvoop-supanels-and-vi-templates/
The .lvlib is likely having minimal impact on your project load time. The expense is generally from the large number of dependencies that your main VI has.
No, I'm not joking. We have found that hard drives these days are so wide in diameter that location on disk has a massive impact on seek times. Of course, this isn't generally under user control.
Blazing fast load speeds regardless of what you're working on. Gets rid of the diameter of disk issue.
The single biggest hit during load is disk seek time, and LLBs solve that by making one file, one file which is optimized for loading the parts of a VI hierarchy. This only helps if you are actually using most or all of the VIs in that LLB.
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.
I assume so. I consider autopopulate folders to be way more trouble than they are worth, so I never use them. But every time the project loads it would have to scan the entire directory and rebuild instead of just reading the file, and then any items that are in libraries have to be moved from their place in the autopopulate directory to their place in the library. That could be a lot of work.
website links
LabVIEW Object-Oriented Programming: The Decisions Behind the Design
http://www.ni.com/white-paper/3574/en/
http://forums.ni.com/t5/LabVIEW/How-to-reduce-project-load-time/td-p/936487
Luc Desruelle | Mon profil | Mon blog LabVIEW | Auteur livre LabVIEW : Programmation et applications - G Web
Certified LabVIEW Architect (CLA) & Certified TestStand Developper (CTD) | LabVIEW Champion
MESULOG - LinkedIn site | NERYS - NERYS Group
| directeur CEO MESULOG
| CODIR - NERYS group
Pour ajouter un commentaire ici, vous devez être inscrit. Si vous êtes déjà inscrit, connectez-vous. Dans le cas contraire, inscrivez-vous puis connectez-vous.