NI Home
Cart Cart | Help
Hello Events Academic NI Developer Zone Support Solutions Products & Services Contact NI MyNI
You are here: 
NI Home > NI Developer Zone > NI Discussion Forums


Reply
Trusted Enthusiast
Darren
Posts: 2,614

Darren's Weekly Nugget 06/21/2010

If you think LabVIEW takes too long to launch, here are a few things you can do to speed it up:

 

  • Uninstall Modules/Toolkits - If there are modules and toolkits installed that you never use, you can uninstall them and speed up LabVIEW launch time.  Even if you have something installed under an evaluation license and the license expires, an expired toolkit/module still adds to launch time.
  • SCC Server Performance - During launch, LabVIEW connects to your Source Code Control server (if you have SCC enabled).  If your server is slow, or gets easily bogged down, this can make your LabVIEW launch much slower.  A faster or more responsive SCC Server is the only solution (other than disabling SCC) for this problem.
  • Skip GSW at Launch - You can select Tools > Options > Environment > General > Skip Getting Started window on launch to have LabVIEW open with a blank VI instead of the Getting Started Window.  On my machine this shaves about 1 second off my LabVIEW launch time.
  • Load palettes in background - This is the default setting for loading palettes (Tools > Options > Control/Functions Palettes > Loading), so if you haven't changed anything, you're good.  But since I have often advocated changing this setting to benefit Quick Drop users (see here), I figured I should mention it for anyone looking for ways to launch LabVIEW as fast as possible.
  • Clear out user.lib and instr.lib - Even if you do load palettes in the background, there are some initial palette loading operations that still must happen during LabVIEW launch.  So the fewer palette items you have, the faster LabVIEW will launch.  If you have unused instrument drivers in instr.lib, or unused libaries in user.lib, it may be a good idea to clear those out.  Another alternative would be to move these items out of user.lib and instr.lib into another location and add that location to your project.  This way, the VIs are still available for use, but they are not in the palettes, and therefore do not affect launch time.

Do you have any other suggestions on how to speed up LabVIEW launch time?  Let's hear them!

Darren Nattinger, CLA
LabVIEW Artisan and Nugget Penman
Active Participant
PhillipBrooks
Posts: 1,105

Re: Darren's Weekly Nugget 06/21/2010

Mass compile your user.lib and instr.lib folders.

 

If the user.lib / instr.lib VI version is earlier than your environment, LabVIEW must recompile these on loading...

 

http://zone.ni.com/reference/en-XX/help/371361B-01/lvhowto/mass_compiling_vis/


Now is the right time to use %^<%Y-%m-%dT%H:%M:%S%3uZ>T
If you don't hate time zones, you're not a real programmer.

"You are what you don't automate"
Inplaceness is synonymous with insidiousness

By using this web site, you accept the Terms of Use for this web site. Please read these Terms of Use carefully before using any part of this site. Please go here for information on ni.com's copyright infringement policy.
My Profile | Privacy | Legal | Contact NI © 2011 National Instruments Corporation. All rights reserved.    |    E-Mail this Page E-Mail this Page