> You might want to read application Note 114 called Using LabVIEW to
> Create Multithreaded VIs for Maximun Performance and Reliability. It
> doesn't spell out how to make LV use dual processors but talks about
> dual processors and multithreading.
> I also have an application that can benefit from dual processor and I
> will be receiving it on Monday I hope. Any way to make a long story
> short I've been on the phone with Tech support about the issue and
> they don't have a lot of good information. It seems to be the general
> consensus that there is an internal document that covers this issue
> but they have yet to locate it and send it to me. The two guys I've
> spoken to feel that LabView automatically detects that you have
processors and uses them as efficiently as possible. I think
> you have to make sure that the two vi's you call simultaniously are on
> different threads.
The paper being looked for might be the presentations made at NIWeek. I
think searching for Inside LabVIEW on the devzone will lead you to the
The answer is that right out of the box, LV will adapt its execution
engines to multiple processors. This will begin to take advantage of
multiple processors, but if the dataflow sequences things into a single
chain of computations, then it will basically move the computation to
one processor and the other to UI. The parallelization can be further
aided by breaking a task into multiple loops or pipelining so that
dataflow defines more than one task at a time.
As always, I'd write the application with the simplest code possible,
then measure the processor usage with the task manager and profiler.
With the simple coding, you can rewrite subVIs or move code around if
necessary to improve things after you measure your code. If you have
questions about improving processor usage, there was another NIWeek
presentation on Multiprocessor usage, or you can ask questions here.