<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://blogs.msdn.com/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>Exploring the Performance of the ADO.NET Entity Framework – Part 2</title><link>http://blogs.msdn.com/adonet/archive/2008/02/11/exploring-the-performance-of-the-ado-net-entity-framework-part-2.aspx</link><description>Query Performance During this post I’ll show a few patterns on how to improve the query performance. A major design element for performance is the query cache. Once a query is executed, parts of the query are maintained in a global cache. Because of query</description><dc:language>en</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>re: Exploring the Performance of the ADO.NET Entity Framework – Part 2</title><link>http://blogs.msdn.com/adonet/archive/2008/02/11/exploring-the-performance-of-the-ado-net-entity-framework-part-2.aspx#7624398</link><pubDate>Tue, 12 Feb 2008 02:45:19 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:7624398</guid><dc:creator>Ryan</dc:creator><description>&lt;p&gt;Do you have any comparison between doing LINQ like &lt;/p&gt;
&lt;p&gt;'from x in y select x;'&lt;/p&gt;
&lt;p&gt;vs.&lt;/p&gt;
&lt;p&gt;'x.Select()'&lt;/p&gt;
&lt;p&gt;More complex queries would be more useful but I am interested in which type is actually faster&lt;/p&gt;
</description></item><item><title>re: Exploring the Performance of the ADO.NET Entity Framework – Part 2</title><link>http://blogs.msdn.com/adonet/archive/2008/02/11/exploring-the-performance-of-the-ado-net-entity-framework-part-2.aspx#7629210</link><pubDate>Tue, 12 Feb 2008 06:01:14 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:7629210</guid><dc:creator>Phil Bolduc</dc:creator><description>&lt;p&gt;I assume you took into consideration the database buffer cache?&lt;/p&gt;
</description></item><item><title>re: Exploring the Performance of the ADO.NET Entity Framework – Part 2</title><link>http://blogs.msdn.com/adonet/archive/2008/02/11/exploring-the-performance-of-the-ado-net-entity-framework-part-2.aspx#7629339</link><pubDate>Tue, 12 Feb 2008 06:05:38 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:7629339</guid><dc:creator>Jim Wooley</dc:creator><description>&lt;p&gt;I'm glad to finally see some EF performance information. It would be helpful to see a comparison against the similar process with a DataReader, DataSet, LINQ to SQL and other OR Mappers to see just what the performance trade-offs are. In this regard, I point to Rico Mariani's series on performance with LINQ to SQL as an example.&lt;/p&gt;
&lt;p&gt;In the case of the examples you've presented so far, the queries are identical to the kind of 1-1 table mapping that is possible with LINQ to SQL. It would be nice to also see some performance on more complex object mapping schemes (multiple tables to single object for example).&lt;/p&gt;
</description></item><item><title>re: Exploring the Performance of the ADO.NET Entity Framework – Part 2</title><link>http://blogs.msdn.com/adonet/archive/2008/02/11/exploring-the-performance-of-the-ado-net-entity-framework-part-2.aspx#7636598</link><pubDate>Tue, 12 Feb 2008 12:22:29 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:7636598</guid><dc:creator>Cosmin</dc:creator><description>&lt;p&gt;Is there any way that we can reduce the time when the first query is run? I thought that using compiled queries would reduce that time.&lt;/p&gt;
&lt;p&gt;Thank you.&lt;/p&gt;
</description></item><item><title>ADO.NET Entity FrameWork Performance</title><link>http://blogs.msdn.com/adonet/archive/2008/02/11/exploring-the-performance-of-the-ado-net-entity-framework-part-2.aspx#7651896</link><pubDate>Tue, 12 Feb 2008 22:33:53 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:7651896</guid><dc:creator>JuST ANOTHER GeeK</dc:creator><description>&lt;p&gt;ADO.NET Entity FrameWork Performance&lt;/p&gt;
</description></item><item><title>re: Exploring the Performance of the ADO.NET Entity Framework – Part 2</title><link>http://blogs.msdn.com/adonet/archive/2008/02/11/exploring-the-performance-of-the-ado-net-entity-framework-part-2.aspx#7660629</link><pubDate>Wed, 13 Feb 2008 05:34:57 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:7660629</guid><dc:creator>juliel</dc:creator><description>&lt;p&gt;Brian&lt;/p&gt;
&lt;p&gt;Thank you so much for going into this detail. I look forward to more.&lt;/p&gt;
</description></item><item><title>EF et performance</title><link>http://blogs.msdn.com/adonet/archive/2008/02/11/exploring-the-performance-of-the-ado-net-entity-framework-part-2.aspx#7673210</link><pubDate>Wed, 13 Feb 2008 16:20:27 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:7673210</guid><dc:creator>Matthieu MEZIL</dc:creator><description>&lt;p&gt;J'ai quelque peu d&amp;#233;laiss&amp;#233; mon blog ces derniers temps mais maintenant que les techdays sont pass&amp;#233;s (du&lt;/p&gt;
</description></item><item><title>Buenas prácticas para contextos de tiempo de vida cortos en ADO.NET Entity Framework BETA3</title><link>http://blogs.msdn.com/adonet/archive/2008/02/11/exploring-the-performance-of-the-ado-net-entity-framework-part-2.aspx#7682278</link><pubDate>Thu, 14 Feb 2008 02:27:21 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:7682278</guid><dc:creator>QuintaStation</dc:creator><description>&lt;p&gt;En este post comento una serie buenas pr&amp;#225;cticas para mejorar la eficiencia de ADO.NET Entity Framework&lt;/p&gt;
</description></item><item><title>re: Exploring the Performance of the ADO.NET Entity Framework – Part 2</title><link>http://blogs.msdn.com/adonet/archive/2008/02/11/exploring-the-performance-of-the-ado-net-entity-framework-part-2.aspx#7725371</link><pubDate>Sat, 16 Feb 2008 03:29:45 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:7725371</guid><dc:creator>Jim L</dc:creator><description>&lt;p&gt;What is the ability to persist this global cache? Given that the abstraction layer probably doesn't change a heck of a lot, there's no need to rebuild it unless it is invalidated. I'd hate to put the user through unneeded work if its not quick.&lt;/p&gt;
</description></item><item><title>re: Exploring the Performance of the ADO.NET Entity Framework – Part 2</title><link>http://blogs.msdn.com/adonet/archive/2008/02/11/exploring-the-performance-of-the-ado-net-entity-framework-part-2.aspx#7775479</link><pubDate>Mon, 18 Feb 2008 18:42:34 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:7775479</guid><dc:creator>Brian Vallelunga</dc:creator><description>&lt;p&gt;I'm very curious about best-practices for an asp.net environment. Obviously, keeping around the compiled query would be great for the performance benefits of subsequent queries, yet in a web scenario, I'm generally creating a context, executing a query, and then destroying both. Is there some advice out there about how to make this more efficient so that I don't pay the 200ms penalty each time?&lt;/p&gt;
</description></item><item><title>re: Exploring the Performance of the ADO.NET Entity Framework – Part 2</title><link>http://blogs.msdn.com/adonet/archive/2008/02/11/exploring-the-performance-of-the-ado-net-entity-framework-part-2.aspx#7778705</link><pubDate>Mon, 18 Feb 2008 22:14:41 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:7778705</guid><dc:creator>JasonBSteele</dc:creator><description>&lt;p&gt;In the stats above it appears that there is a decrease in performance for the &amp;quot;No Tracking&amp;quot; in several scenarios for the first run. For example, in the LINQ no parameters scenario the Tracking time is 202, whereas the No Tracking time is 282.&lt;/p&gt;
&lt;p&gt;Is it true that No Tracking is actually slower in some cases, and if so why?&lt;/p&gt;
&lt;p&gt;Many Thanks&lt;/p&gt;
</description></item><item><title>推荐系列：2008年第06期 总8期</title><link>http://blogs.msdn.com/adonet/archive/2008/02/11/exploring-the-performance-of-the-ado-net-entity-framework-part-2.aspx#7819325</link><pubDate>Wed, 20 Feb 2008 18:23:31 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:7819325</guid><dc:creator>TerryLee</dc:creator><description>&lt;p&gt;概述春节后的第一期推荐系列文章，共有10篇文章：1.ASP.NETMVCExampleApplicationoverNorthwindwiththeEntityFramework...&lt;/p&gt;
</description></item><item><title>Rendimiento de Entity Framework II</title><link>http://blogs.msdn.com/adonet/archive/2008/02/11/exploring-the-performance-of-the-ado-net-entity-framework-part-2.aspx#7821153</link><pubDate>Wed, 20 Feb 2008 20:44:08 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:7821153</guid><dc:creator>El blog de Vicente</dc:creator><description>&lt;p&gt;Como hace unos d&amp;#237;as apuntaba Unai , en el blog del equipo de desarrollo de ADO.NET est&amp;#225;n publicando una&lt;/p&gt;
</description></item><item><title>【收藏】推荐系列：2008年第06期 总8期 </title><link>http://blogs.msdn.com/adonet/archive/2008/02/11/exploring-the-performance-of-the-ado-net-entity-framework-part-2.aspx#7826848</link><pubDate>Thu, 21 Feb 2008 04:33:56 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:7826848</guid><dc:creator>Jacky_Xu</dc:creator><description>&lt;p&gt;概述 春节后的第一期推荐系列文章，共有10篇文章： 1.ASP.NETMVCExampleApplicationoverNorthwindwiththeEntityFr...&lt;/p&gt;
</description></item><item><title>Brian Dawson posts second ADO.NET Entity Framework Query Performance blog post</title><link>http://blogs.msdn.com/adonet/archive/2008/02/11/exploring-the-performance-of-the-ado-net-entity-framework-part-2.aspx#7841949</link><pubDate>Fri, 22 Feb 2008 00:28:20 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:7841949</guid><dc:creator>Hot Topics</dc:creator><description>&lt;p&gt;The first post, Exploring the Performance of the ADO.NET Entity Framework - Part 1 , began: Performance&lt;/p&gt;
</description></item><item><title>re: Exploring the Performance of the ADO.NET Entity Framework – Part 2</title><link>http://blogs.msdn.com/adonet/archive/2008/02/11/exploring-the-performance-of-the-ado-net-entity-framework-part-2.aspx#8130853</link><pubDate>Mon, 10 Mar 2008 15:16:15 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:8130853</guid><dc:creator>Ayman Saleh</dc:creator><description>&lt;p&gt;Do you have any performance statistics relating to using SQL Server stored procedures?&lt;/p&gt;
</description></item><item><title>re: Exploring the Performance of the ADO.NET Entity Framework – Part 2</title><link>http://blogs.msdn.com/adonet/archive/2008/02/11/exploring-the-performance-of-the-ado-net-entity-framework-part-2.aspx#8171194</link><pubDate>Wed, 12 Mar 2008 19:12:43 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:8171194</guid><dc:creator>TJE</dc:creator><description>&lt;p&gt;I love all the amazing work that has been done with the ADO.NET Entity Framework and Data Services. &amp;nbsp;There is one piece that I can't find any information on, however: &amp;nbsp;Support for multi domain models or multiple databases in the Entity Framework (and thus Data Services).&lt;/p&gt;
&lt;p&gt;We have 10+ large enterprise databases all hosted on the same server/instance of sql server and these databases are somewhat used as &amp;quot;schema&amp;quot; conatiners, i.e. we have many stored procedures that make calls to stored procedures/tables/views in another database and there are logical relationships between tables in different databases. &amp;nbsp;This requires our Entity Model to have entity relationships across databases and thus across Entity Models (since, AFAIK, currently the Entity Framework design surface can only include tables from one database).&lt;/p&gt;
&lt;p&gt;I believe that this is a big weakness and needs to be addressed as soon as possible. &amp;nbsp;The other issue I have is how much the Entity Framework design surface slows down (and the entity boxes become unmanageble from a visual real-estate perspective) after about 20-30 tables on it...&lt;/p&gt;
&lt;p&gt;Any comments on this from the Entity Framework team would be very much appreciated...&lt;/p&gt;
</description></item><item><title>re: Exploring the Performance of the ADO.NET Entity Framework – Part 2</title><link>http://blogs.msdn.com/adonet/archive/2008/02/11/exploring-the-performance-of-the-ado-net-entity-framework-part-2.aspx#8289605</link><pubDate>Mon, 17 Mar 2008 17:52:25 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:8289605</guid><dc:creator>Paymon</dc:creator><description>&lt;p&gt;Great post!&lt;/p&gt;
&lt;p&gt;It will be helpful if you could also include comparison metrics from the DBMS side.&lt;/p&gt;
&lt;p&gt;Splitting the execution time between application (CLR) and Sql server (DBMS) for each thread will also be of a huge help in understanding and tuning performance.&lt;/p&gt;
&lt;p&gt;Thanks&lt;/p&gt;
</description></item><item><title>re: Exploring the Performance of the ADO.NET Entity Framework – Part 2</title><link>http://blogs.msdn.com/adonet/archive/2008/02/11/exploring-the-performance-of-the-ado-net-entity-framework-part-2.aspx#8326090</link><pubDate>Wed, 19 Mar 2008 21:53:30 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:8326090</guid><dc:creator>Brian Dawson - MSFT</dc:creator><description>&lt;p&gt;Thanks for all the comments and questions! &amp;nbsp;It's great to see the interest in the Entity Framework. I'm working on another post about performance that I'll try to post soon. It addresses some of the questions.&lt;/p&gt;
&lt;p&gt;-Brian&lt;/p&gt;
</description></item><item><title>re: Exploring the Performance of the ADO.NET Entity Framework – Part 2</title><link>http://blogs.msdn.com/adonet/archive/2008/02/11/exploring-the-performance-of-the-ado-net-entity-framework-part-2.aspx#8326994</link><pubDate>Thu, 20 Mar 2008 08:48:09 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:8326994</guid><dc:creator>Ranga</dc:creator><description>&lt;p&gt;Is there any news on the Release Date of Entity Framework?&lt;/p&gt;
</description></item><item><title>ADO.NET Entity Framework Performance Comparison</title><link>http://blogs.msdn.com/adonet/archive/2008/02/11/exploring-the-performance-of-the-ado-net-entity-framework-part-2.aspx#8340746</link><pubDate>Fri, 28 Mar 2008 04:48:40 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:8340746</guid><dc:creator>ADO.NET team blog</dc:creator><description>&lt;p&gt;There have been a few questions from the last performance blog post about how the Entity Framework compares&lt;/p&gt;
</description></item><item><title>EF : deux nouveaux posts de l'ADO .Net Team</title><link>http://blogs.msdn.com/adonet/archive/2008/02/11/exploring-the-performance-of-the-ado-net-entity-framework-part-2.aspx#8341265</link><pubDate>Fri, 28 Mar 2008 11:53:56 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:8341265</guid><dc:creator>Matthieu MEZIL</dc:creator><description>&lt;p&gt;L'ADO .Net Team vient de poster deux nouveaux posts : le premier concerne l'utilisation des proc&amp;#233;dures&lt;/p&gt;
</description></item><item><title>Entity Framework: How Referential Integrity Works</title><link>http://blogs.msdn.com/adonet/archive/2008/02/11/exploring-the-performance-of-the-ado-net-entity-framework-part-2.aspx#8549427</link><pubDate>Sun, 25 May 2008 01:01:05 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:8549427</guid><dc:creator>Damir Dobric Posts</dc:creator><description>&lt;p&gt;For everybody who is interested on internals of Entity Framework (ER) in relation to referential integrity&lt;/p&gt;
</description></item><item><title>ADO.NET team blog : Exploring the Performance of the ADO.NET Entity Framework – Part 2</title><link>http://blogs.msdn.com/adonet/archive/2008/02/11/exploring-the-performance-of-the-ado-net-entity-framework-part-2.aspx#8567613</link><pubDate>Sun, 01 Jun 2008 16:33:24 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:8567613</guid><dc:creator>Dating</dc:creator><description>&lt;p&gt;Query Performance During this post I’ll show a few patterns on how to improve the query performance. A major design element for performance is the query cache. Once a query is executed, parts of the query are maintained in a global cache. Because of quer&lt;/p&gt;
</description></item><item><title>ADO.NET team blog : Exploring the Performance of the ADO.NET Entity Framework – Part 2</title><link>http://blogs.msdn.com/adonet/archive/2008/02/11/exploring-the-performance-of-the-ado-net-entity-framework-part-2.aspx#8575578</link><pubDate>Thu, 05 Jun 2008 19:08:15 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:8575578</guid><dc:creator>Weddings</dc:creator><description>&lt;p&gt;Query Performance During this post I’ll show a few patterns on how to improve the query performance. A major design element for performance is the query cache. Once a query is executed, parts of the query are maintained in a global cache. Because of quer&lt;/p&gt;
</description></item><item><title>re: Exploring the Performance of the ADO.NET Entity Framework – Part 2</title><link>http://blogs.msdn.com/adonet/archive/2008/02/11/exploring-the-performance-of-the-ado-net-entity-framework-part-2.aspx#8738632</link><pubDate>Wed, 16 Jul 2008 16:59:47 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:8738632</guid><dc:creator>André Magalhães</dc:creator><description>&lt;p&gt;Analyzing the test results, to use compiled LINQ queries is better than non-compiled LINQ queries only in the second execution. In the first execution the compiled LINQ queries are always slower. &lt;/p&gt;
&lt;p&gt;But what is exactly the second execution? Is an execution using the same instance of the objectcontext or is an execution in a new thread with a new objectcontext?&lt;/p&gt;
&lt;p&gt;What I mean is, does the query cache survive between different threads or it is alive just during a thread execution lifetime?&lt;/p&gt;
</description></item><item><title>re: Exploring the Performance of the ADO.NET Entity Framework – Part 2</title><link>http://blogs.msdn.com/adonet/archive/2008/02/11/exploring-the-performance-of-the-ado-net-entity-framework-part-2.aspx#8883732</link><pubDate>Thu, 21 Aug 2008 09:50:39 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:8883732</guid><dc:creator>Podlipensky</dc:creator><description>&lt;p&gt;Do you have comparsion data for EF with stored procedures and standalone stored procedures? Does it have some perfomance difference?&lt;/p&gt;
</description></item><item><title>Make your Entity Framework model faster (with EdmGen2)</title><link>http://blogs.msdn.com/adonet/archive/2008/02/11/exploring-the-performance-of-the-ado-net-entity-framework-part-2.aspx#9306088</link><pubDate>Sun, 11 Jan 2009 20:40:19 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9306088</guid><dc:creator>Jiří {x2} Činčura</dc:creator><description>&lt;p&gt;If we’ll skip exact details, we can say, that internal behavior of whole modeling and mapping is based&lt;/p&gt;
</description></item></channel></rss>