Skip to main content

How to Improve Linq Query Performance by using Parallel/ PLinq

How to Improve Linq Query Performance by using Parallel/ PLinq

I want to highlight the disadvantage first, because if you know the disadvantage you can make a choice if required in your project or not.

Don't use if you have a Single core or dual core CPU's. I found that depending on the complexity of For loop  the CPU performance reaches more than 70-80%  (Not talking about the simple For loop). So if you want to use the parallelism for complex loop make sure you have more than  2 CPU's
Parallelization sometimes cause a  PLinq query to run slower than Linq to object equivalent. Basically it said like queries with few data source elements and fast user delegates are reluctant to speed up much.

Parallel Linq is the parallel implementation of Linq. Parallel Linq implementation on loops provide better performance compared to sequential  loop. Parallel Linq also works like Linq queries operate on any in-memory IEnumerale(of T) data source. PLINQ make full use of all processors on the system. The parallelism is achieved by diving the data source into multiple segments and working each segment on different worker threads on multiple processor.

MaxDegreeOfParallelism  - Upper limit of number of processors irrespective of number of cores(We can only specify the maximum )limit.. So even if also if we don't use the CPU , no extra task will run in parallel. 

Implementation 

List testModelList=GetTestModelList();

Parallel.ForEach(testModelList,
                new ParallelOptions { MaxDegreeOfParallelism = 5 },
                tm=>; {//Do Operations
                  
              });


Reference:http://msdn.microsoft.com/en-us/library/dd460688.aspx

Comments

Popular posts from this blog

How to write secure mvc application using encrypting URL

There are lots ways available to write the secure Mvc application. In my experience I came across lots of secure application in public facing. I want to tell about some of the mechanism I followed. 1- encrypting the URL Parameters and preserving id's encrypted on the client side 1- I always make sure if I pass Id or any sensitive data into the view always make sure it's encrypted. By doing so make sure if we forced to use HTML.hidden or HTML.hidden for have the encrypted values, in action link if I pass any parameters from the client side (eg:- edit or create or navigating between different actions we can make sure that all the values are encrypted) During the design of the actions results if it's http get I usually encrypt the sensitive data [httpget] Public actionresult display() { TestModel testModel=new TestModel(); testModel.id= encrypt(id); Return View(testModel); } [httppost] Public ActionResult Display(string id) { Guid d_id= new Guid(decrypt(id));

Single page application (SPA) using ext.js

what is spa? Single page application are applications that fit in one page with rich and fluid user experiences like a desktop based applications. Why is SPA? All web based elements (html, CSS,javascript) are downloaded from the server on single page load and avoid the continuous page post back. i can explain what this mean. Suppose your web application is made of certain flow and it consists of 5 different pages. Each page need to get data from the user and save before moving to the next page. So when we navigate from one page to other it need to make a round trip to server to store the data in one page and get the data for the next page to display. but in spa we can avoid the continuous post backs. The whole page will not post back any time other than the first load. But it communicate to the server dynamically behind the scene and can achieve the same functionality. Spa using ext.js designing a SPA using ext.js is a challenging task if you are unaware about the ext.js

Sql Server Internals - Named Pipes

Named pipes enables clients applications to request a reliable and two way connection between the client application and Sql Server, across a network. A named pipe has a name which follows the UNC naming convention : \\Server\pipe\name The default names pipe for SQL server is :                 \\Server\pipe\sql\query A named instance would have a named pipe of                \\server\pipe\MSSQL$instancename\sql\query Early versions of SQL Server only provided Named Pipes. Named Pipes also allows for impersonation of a clients credentials. The feature is used by SQL server when using Linked Servers. The clients logon credentials are passed across to the Linked Server for authentication. Named Pipes can operate over TCP/IP, NETBEUI or IPX as it indirectly relies on the Common Internet Files Sytems