Visual Basic® 2010 Unleashed

Ordering Sequences

One of the most important consequences of Parallel LINQ (and, more generally, of parallel computing) is that processing is not done sequentially as it would happen on single-threaded code. This is because multiple threads run concurrently. To understand this, the following is an excerpt from the iteration on the result of the parallel query:

You would probably instead expect something like the following, which is produced by the classic LINQ query:

If you need to work in sequential order but you do not want to lose the capabilities ...