How does LabView choose which core to use in a multi-core system

[nighthawk]

I have to share my multi-core processor with another application.  When this other application runs, it consumes 100% of one of the cores on the system for several seconds.  I am worried about this other application blocking part of my control code, resulting in delayed control signals and possible loss of control. 

1.  When one core is completely occupied, will LabVIEW put all operations into the other core? (I am guessing this is yes)

2.  If an operation is occurring on a core that is subsequently 100% subscribed, will LabVIEW move the operation to another core?  Does LabVIEW (or XP) prevent the other application from stalling operations already in progress? 

The operations I am most concerned with are for the Multifunction DAQ and serial port calls.   

I am working on a good sized (>100 vi) control system application in LabVIEW 8.2.1.  It is running on Windows XP.   

[Chris_VH]

1. Yes, Windows will allocate LabVIEW to an open thread on the unused core.

2. Again, yes, Windows will check for available threads and move LabVIEW to any that are open, it doesn't matter what core that is.

You can also force LabVIEW code, or parts of it, to run on a specific processor using the timed loop structure. You can find help for setting that up here.