One of the recent great additions to LV (for me at least) was the parallel for-loop. This is a great and quick way to essentially generate a worker pool.
The only drawback I see is that we need to know the total number of iterations in advance which can mostly be OK but .
By allowing essentially the same function for a while loop we can spawn parallel processing workers for an indefinite period. For operations which can be spread over multiple cores and whose execution order is not important (or whose order can be re-created afterwards) this can be very tasty indeed.
An application I have is the processing of data which is being input via Queue and whose output can be sent also by Queue (as a part of the incoming queue data). I don't care which worker processes which queue entry as long as they run in parallel and the output goes to the right place.
I abuse this a bit at the moment as can be seen in THIS post. This approach is limited by the neccessity to know the total number of loop iterations in advance.
Shane.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Any idea that has received less than 2 kudos within 2 years after posting will be automatically declined.