LabView task priority and concurrent tasks on Win2K

Question

When doing some number crunching with LabVIEW, my program is
using all CPU time on my Win2K desktop. Even when I have some
other programs running in the background (like setiathome...)
with the same taskpriority as LabVIEW, LabVIEW is using all the
CPU time for its calculations. Normally it should share the
CPU with all other tasks of the same priority, as I understand
the task scheduling of Windows. Why doesn't work LabVIEW this way?

Answer 1

> When doing some number crunching with LabVIEW, my program is
> using all CPU time on my Win2K desktop. Even when I have some
> other programs running in the background (like setiathome...)
> with the same taskpriority as LabVIEW, LabVIEW is using all the
> CPU time for its calculations. Normally it should share the
> CPU with all other tasks of the same priority, as I understand
> the task scheduling of Windows. Why doesn't work LabVIEW this way?
LV does work that way. By default the execution takes place in threads
that are the same priority as the LV process. If the LV process is
lowered in priority, so are its threads, and vice versa. It is possible
to set LV threads to be a few priority marks above or below this, so one
thing to check is to see wh
at the priority of the VI is set to.
Also, Seti may always decide to execute in threads that are a lower
priority than its process. It is possible to set process priorities to
try and better balance these out, if that is your goal.
Greg McKaskle