zoukankan      html  css  js  c++  java
  • Application analysis: Northwind.NET

    For an article I am writing, I wanted to compare a RavenDB model to a relational model, and I stumbled upon the following Northwind.NET project.

    I plugged in the Entity Framework Profiler and set out to watch what was going on. To be truthful, I expected it to be bad, but I honestly did not expect what I got. Here is a question, how many queries does it take to render the following screen?

    image

    The answer, believe it or no, is 17:

    image

    You might have noticed that most of the queries look quite similar, and indeed, they are. We are talking about 16(!) identical queries:

    SELECT [Extent1].[ID]           AS [ID],        [Extent1].[Name]         AS [Name],        [Extent1].[Description]  AS [Description],        [Extent1].[Picture]      AS [Picture],        [Extent1].[RowTimeStamp] AS [RowTimeStamp] FROM   [dbo].[Category] AS [Extent1]

    Looking at the stack trace for one of those queries led me to:

    image

    And to this piece of code:

    image

    You might note that dynamic is used there, for what reason, I cannot even guess. Just to check, I added a ToArray() to the result of GetEntitySet, and the number of queries dropped from 17 to 2, which is more reasonable. The problem was that we passed an IQueryable to the data binding engine, which ended up evaluating the query multiple times.

    And EF Prof actually warns about that, too:

    image

    At any rate, I am afraid that this project suffer from similar issues all around, it is actually too bad to serve as the bad example that I intended it to be.

  • 相关阅读:
    Bridage
    国内项目测试培训笔录和小结
    Proxy
    数据库设计
    PDF转Word
    机务维修成本技术点
    MyEclipse10
    MyEclips:Struts 2 + Hibernate 4 + SQL Server2008
    观察者模式
    javascript事件设计模式
  • 原文地址:https://www.cnblogs.com/shihao/p/2320396.html
Copyright © 2011-2022 走看看