LINQ Performance Pitfall - Deferred Execution

re: LINQ Performance Pitfall - Deferred Execution

Omer van Kloeten — Sat, 31 May 2008 18:37:22 GMT

Philip,

It is true that the standard of LINQ is deferred execution, but it's not a rule. Also, as Oren (Ayende) said above, multiple statements sent to a database may be optimized better than you optimizing for it with .ToArray() calls.

re: LINQ Performance Pitfall - Deferred Execution

Philip — Sat, 31 May 2008 14:59:51 GMT

This is very true of LINQ in all incarnations (Object, XML, and SQL). Even LINQ to SQL table calls perform deferred execution.

I think this is going to be one of the most difficult things for people new to LINQ to get their head around. We are going to be seeing a lot of problems in code before people think about deferred execution.

Dew Drop - May 28, 2008 | Alvin Ashcraft's Morning Dew

Dew Drop - May 28, 2008 | Alvin Ashcraft's Morning Dew — Wed, 28 May 2008 15:02:13 GMT

Pingback from Dew Drop - May 28, 2008 | Alvin Ashcraft's Morning Dew

Interesting Finds: May 28, 2008

Jason Haley — Wed, 28 May 2008 14:14:51 GMT

re: LINQ Performance Pitfall - Deferred Execution

Omer van Kloeten — Wed, 28 May 2008 05:09:07 GMT

Totally agree. This is only always true for LINQ to Objects and each other case of LINQ should be examined on its own accord.

re: LINQ Performance Pitfall - Deferred Execution

Ayende Rahien — Tue, 27 May 2008 21:38:47 GMT

Note that this is only true for Linq statement that run in memory.

If this is being sent to a DB or another location for execution, this would probably much better to let that location to handle this.