I don't believe this is the case; my confusion is due to the fact that the literature with regards to this structure discusses using the maximum # of cores the computer in which this codemay run in the For Loop Iteration Parallelism dialog box as well as using the CPU Information function to determine how many instances to parallelize. I suspect parallel For Loops will first be decomposed into iteration clumps/tasks which will either be cooperatively multitasked &/or multithreaded within the same prioritized execution system before they ever get to be mapped to dedicated cores per instance. Is this correct? - the literature I refer to is Improving Performance with Parallel Loops http://zone.ni.com/devzone/cda/tut/p/id/9393, under Performance Tips or the LabVIEW Help (Multiprocessing and Hyperthreading in LabVIEW). I just don't see how this information applies to how the loop instances are parallelized and executed. I hope someone can enlighten me and perhaps others reading these docs. Thank you !

jorgeinSD, thanks for the insightful question. Your second possibility is correct. Each parallel loop instance is in a different clump, and the execution system schedules those clumps among the available threads. LabVIEW does not bind threads to cores for the Parallel For Loop, so the threads may switch between cores as they execute. Mary Fletcher Software Engineer LabVIEW R&D

LabVIEW

Do Parallel For Loops run on dedicated CPU cores?

Solved!

JorgeinSD, LabVIEW creates the maximum of four and the number of logical processors on your machine for each execution system, unless you configured the number of threads using vi.lib\Utility\sysinfo.llb\threadconfig.vi.

Message 11 of 11

(423 Views)

LabVIEW

Do Parallel For Loops run on dedicated CPU cores?

Re: Do Parallel For Loops run on dedicated CPU cores?