LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

How to create parallel tasks using parallel for loops

Solved!
Go to solution

Hi Mary,

 

Okay, so the bottom line is: if you exceed the number of threads that the LabVIEW execution system uses, then you should check if performance increases or not.

 

I am working on setting that up right now, so I will see what happens and post the results here.

Could you sketch a typical situation for which more threads isn't better and one for which more threads do help?

 

Regards,

Frans 

0 Kudos
Message 11 of 12
(1,103 Views)

Frans Wijnen wrote:

Hi Mary,

 

Okay, so the bottom line is: if you exceed the number of threads that the LabVIEW execution system uses, then you should check if performance increases or not.

 

I am working on setting that up right now, so I will see what happens and post the results here.

Could you sketch a typical situation for which more threads isn't better and one for which more threads do help?

 

Regards,

Frans 


Having more threads than cores will typically not improve performance for computationally-intense applications. For those applications, context switching just creates overhead, since there will be no benefit from replacing a thread that is busy computing with another thread. However, having more threads than cores can improve performance for IO-bound applications where the threads spend part of their time sitting idle. When one thread is idle, it can be swapped out for another thread that can get additional work done.

Message 12 of 12
(1,085 Views)