<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	>
<channel>
	<title>Comments on: How NOT To Optimize LINQ Statements</title>
	<atom:link href="http://www.coderjournal.com/index.php/2008/09/how-not-to-optimize-linq/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.coderjournal.com/2008/09/how-not-to-optimize-linq/</link>
	<description>while(!(succeed = try()));</description>
	<pubDate>Tue, 06 Jan 2009 02:11:05 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.7</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Weekly Link Post 61 &#171; Rhonda Tipton&#8217;s WebLog</title>
		<link>http://www.coderjournal.com/2008/09/how-not-to-optimize-linq/comment-page-1/#comment-16101</link>
		<dc:creator>Weekly Link Post 61 &#171; Rhonda Tipton&#8217;s WebLog</dc:creator>
		<pubDate>Sun, 28 Sep 2008 23:49:39 +0000</pubDate>
		<guid isPermaLink="false">http://www.coderjournal.com/?p=272#comment-16101</guid>
		<description>[...] Nick Berardi has posted on How NOT To Optimize LINQ Statements.&#160; [...]</description>
		<content:encoded><![CDATA[<p>[...] Nick Berardi has posted on How NOT To Optimize LINQ Statements.&nbsp; [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dew Drop - September 25, 2008 &#124; Alvin Ashcraft's Morning Dew</title>
		<link>http://www.coderjournal.com/2008/09/how-not-to-optimize-linq/comment-page-1/#comment-15909</link>
		<dc:creator>Dew Drop - September 25, 2008 &#124; Alvin Ashcraft's Morning Dew</dc:creator>
		<pubDate>Thu, 25 Sep 2008 11:46:27 +0000</pubDate>
		<guid isPermaLink="false">http://www.coderjournal.com/?p=272#comment-15909</guid>
		<description>[...] How Not to Optimize LINQ Statements (Nick Berardi) [...]</description>
		<content:encoded><![CDATA[<p>[...] How Not to Optimize LINQ Statements (Nick Berardi) [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jemm</title>
		<link>http://www.coderjournal.com/2008/09/how-not-to-optimize-linq/comment-page-1/#comment-15904</link>
		<dc:creator>Jemm</dc:creator>
		<pubDate>Thu, 25 Sep 2008 07:28:54 +0000</pubDate>
		<guid isPermaLink="false">http://www.coderjournal.com/?p=272#comment-15904</guid>
		<description>I'd just write and optimize the query manually as a stored procedure as the LINQ (or any other ORM) in situations like these. Easier than trying to bend the tool to achieve the same thing.</description>
		<content:encoded><![CDATA[<p>I&#8217;d just write and optimize the query manually as a stored procedure as the LINQ (or any other ORM) in situations like these. Easier than trying to bend the tool to achieve the same thing.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Reflective Perspective - Chris Alcock &#187; The Morning Brew #187</title>
		<link>http://www.coderjournal.com/2008/09/how-not-to-optimize-linq/comment-page-1/#comment-15903</link>
		<dc:creator>Reflective Perspective - Chris Alcock &#187; The Morning Brew #187</dc:creator>
		<pubDate>Thu, 25 Sep 2008 07:20:58 +0000</pubDate>
		<guid isPermaLink="false">http://www.coderjournal.com/?p=272#comment-15903</guid>
		<description>[...] How NOT To Optimize LINQ Statements - Nick Berardi tells of an unsuccessful attempt to optimise the SQL produced by Linq to SQL by changing the query. Optimisation is always the hardest part of using any ORM. [...]</description>
		<content:encoded><![CDATA[<p>[...] How NOT To Optimize LINQ Statements - Nick Berardi tells of an unsuccessful attempt to optimise the SQL produced by Linq to SQL by changing the query. Optimisation is always the hardest part of using any ORM. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: JV</title>
		<link>http://www.coderjournal.com/2008/09/how-not-to-optimize-linq/comment-page-1/#comment-15878</link>
		<dc:creator>JV</dc:creator>
		<pubDate>Wed, 24 Sep 2008 20:37:18 +0000</pubDate>
		<guid isPermaLink="false">http://www.coderjournal.com/?p=272#comment-15878</guid>
		<description>LINQ TO SQL is a pain in the ass to optimize (as ar most o/r mappers), basicly because you are so far away from the actually SQL which is used and as you show less sql, doesn't mean faster sql.

If your LINQ query doesn't fits your performance needs, use something else..</description>
		<content:encoded><![CDATA[<p>LINQ TO SQL is a pain in the ass to optimize (as ar most o/r mappers), basicly because you are so far away from the actually SQL which is used and as you show less sql, doesn&#8217;t mean faster sql.</p>
<p>If your LINQ query doesn&#8217;t fits your performance needs, use something else..</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Joel</title>
		<link>http://www.coderjournal.com/2008/09/how-not-to-optimize-linq/comment-page-1/#comment-15863</link>
		<dc:creator>Joel</dc:creator>
		<pubDate>Wed, 24 Sep 2008 15:54:55 +0000</pubDate>
		<guid isPermaLink="false">http://www.coderjournal.com/?p=272#comment-15863</guid>
		<description>Had your original LINQ statement been the 2nd one, your refactoring would've been a huge improvement, so I wouldn't say the moral is to just trust the SQL that LINQ generates.  In fact I'd say it's the opposite - there is plenty to optimize even at such a high level of abstraction as LINQ provides, and the table design and indexing will have a lot to do with what LINQ syntax performs best.  Good story!</description>
		<content:encoded><![CDATA[<p>Had your original LINQ statement been the 2nd one, your refactoring would&#8217;ve been a huge improvement, so I wouldn&#8217;t say the moral is to just trust the SQL that LINQ generates.  In fact I&#8217;d say it&#8217;s the opposite - there is plenty to optimize even at such a high level of abstraction as LINQ provides, and the table design and indexing will have a lot to do with what LINQ syntax performs best.  Good story!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: DotNetKicks.com</title>
		<link>http://www.coderjournal.com/2008/09/how-not-to-optimize-linq/comment-page-1/#comment-15855</link>
		<dc:creator>DotNetKicks.com</dc:creator>
		<pubDate>Wed, 24 Sep 2008 12:37:50 +0000</pubDate>
		<guid isPermaLink="false">http://www.coderjournal.com/?p=272#comment-15855</guid>
		<description>&lt;strong&gt;How NOT To Optimize LINQ Statements...&lt;/strong&gt;

You've been kicked (a good thing) - Trackback from DotNetKicks.com...</description>
		<content:encoded><![CDATA[<p><strong>How NOT To Optimize LINQ Statements&#8230;</strong></p>
<p>You&#8217;ve been kicked (a good thing) - Trackback from DotNetKicks.com&#8230;</p>
]]></content:encoded>
	</item>
</channel>
</rss>
