title: Is it worth using PLINQ with ASP.NET?
body: <p>Does anyone have experience using PLINQ with ASP.NET?  Is this a good combination, or something to avoid in most situations?</p>
  
  <p>I develop an intranet ASP.NET site for a lawfirm (~100 users).  Several pages include non-trivial LINQ code, for example, we have a bank rec page that compares thousands of financial transactions between our accounting database and the bank's data, using LINQ to Datasets.  This is slow, so I am tempted to try PLINQ, but I am worried this could lead to 1 request monopolizing the web server.  Having the bank rec run 4 times faster but shutting all other users out while it is running would not be an improvement.</p>
  
  <p>I know there are much faster solutions than LINQ, but I would rather have short code to maintain.</p>
  
  <p>Right now, we have a Dual Pentium 4 web server, but I am hoping we can upgrade to decent hardware in the near future.</p>