Language Integrated Query (LINQ) is a feature introduced in .NET Framework 3.5 which, helps in querying various data sources like the in-memory objects, SQL databases and XMLs. LINQ to objects is the most commonly used one across most applications. It performs the query against an in-memory collection in a sequential manner. In .NET Framework 4.0, as part of the parallel programming features, Parallel LINQ (PLINQ) has been introduced. It is a parallel implementation of querying on collections. This takes care of dividing the collection into subsets and spawning new threads for processing each set of records. It differs from the normal threading operation by running these tasks parallel on different processors available on the machine. Parallel LINQ makes maximum use of a multi-core processor. In most of the scenarios Parallel LINQ is supposed to bring a good amount of increase in the performance but in some cases a sequential operation would be a better option. I will highlight some cases where PLINQ can slow down the performance under the "Things to Consider" section later in this article.


Read More...


I guess you came to this post by searching similar kind of issues in any of the search engine and hope that this resolved your problem. If you find this tips useful, just drop a line below and share the link to others and who knows they might find it useful too. 

Stay tuned to my blog, twitter or facebook to read more articles, tutorials, news, tips & tricks on various technology fields. Also Subscribe to our Newsletter with your Email ID to keep you updated on latest posts. We will send newsletter to your registered email address. We will not share your email address to anybody as we respect privacy.