View Single Post
  #4   Spotlight this post!  
Unread 12-01-2014, 08:27
Greg McKaskle Greg McKaskle is offline
Registered User
FRC #2468 (Team NI & Appreciate)
 
Join Date: Apr 2008
Rookie Year: 2008
Location: Austin, TX
Posts: 4,752
Greg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond repute
Re: Build/run as startup time

You are correct that the compile and build portion of LV is limited to being single threaded. What you may want to experiment with is whether you keep your VIs open when you build, or whether you close them first and then build.

My computer is in a weird state at the moment with other projects, so I wouldn't trust my numbers anyway.

The build loads all of your VIs and the libraries into a build context. If the VIs are in memory, it transfers those from the intel context to the PPC context, compiling and loading alternate libraries as needed from disk.

If the VIs are kicked out of memory, the VIs will all be loaded from disk into the new context. From what I saw last year, both routes performed compiles they didn't need to, but the bugs were reported and some of the biggest ones were fixed. My suspicion is that the disk route will be faster, but it would be helpful to do both and please post your results.

Greg McKaskle
Reply With Quote