Does LINQ improves performance

Question

3.75/5 (3 votes)

See more:

Want your views on whether LINQ provides better performance (compared to say loop constructs like foreach) or it's just a syntactic sugar feature of the framework. I've been using LINQ from quite some day and got conflicting views from my seniors on the topic.
If you can provide some insights.

Posted 11-Jun-11 20:18pm

RakeshMeena

Updated 11-Jun-11 20:45pm

v3

Add a Solution

Comments

Sergey Alexandrovich Kryukov 12-Jun-11 2:40am

Did you ask yourself a simple question: improved (or degrades) performance -- compared to what?
--SA

RakeshMeena 12-Jun-11 2:43am

My mistake. Edited the question.

Sergey Alexandrovich Kryukov 12-Jun-11 23:20pm

Thank you. Answered.
--SA

2 solutions

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Sergey Alexandrovich Kryukov · Answer 1 · 2011-06-11T21:19:00

Solution 1

You can easily compare performance for such simple cases yourself using the class System.Diagnostics.Stopwatch, which provides very good accuracy. My prediction: if you program you loops correctly, you won't find any significant difference if any at all. Let's check it up!

—SA

Posted 11-Jun-11 21:19pm

Sergey Alexandrovich Kryukov

Tarun.K.S · Answer 2 · 2011-06-12T02:40:00

Hi Rakesh,

It depends. For ex: for a simple for-each loop, using LINQ is not necessary, instead it can give more overhead. But using for-each where you want to add additional filtering and grouping, then it will be slow, it would be better to use a LINQ query in such conditions.

That was about Linq to Objects. Considering the case where you want to use Linq to Sql, I would like to recommend this 5-part series article regarding the performance of Linq to SQL : http://blogs.msdn.com/b/ricom/archive/2007/06/22/dlinq-linq-to-sql-performance-part-1.aspx[^].

About Linq to XML, I'm not sure about the performance but its very easy to create XmlElement compared to the functionality provided by XmlDocument class. Its also easy to traverse and filter through the XML, also it has support to XPath expression using the XPathNavigator.
:)