Why Entity Framework performs faster than Dapper in direct select statement [closed]

by

ORM (Object Relational Mapper) is a tool that creates layer between your application and data source and returns you the relational objects instead of
(in terms of c# that you are using) ADO.NET objects. This is basic thing that every ORM does.

To do this, ORMs generally execute the query and map the returned DataReader to the POCO class. Dapper is limited up to here.

To extend this further, some ORMs (also called “full ORM”) do much more things like generating query for you to make your application database independent, cache your data for future calls, manage unit of work for you and lot more. All these are good tools and adds value to ORM; but it comes with cost. Entity Framework falls in this class.

To generate the query, EF have to execute additional code. Cache improves the performance but managing the cache needs to execute additional code. Same is true for unit of work and any other add-on feature provided by EF. All this saves you writing additional code and EF pays the cost.

And the cost is performance. As Dapper does very basic job, it is faster; but you have to write more code. As EF does much more than that, it is (bit) slower; but you have to write less code.

So why your tests show opposite results?
Because the tests you are executing are not comparable.

Full ORMs have many good features as explained above; one of them is UnitOfWork. Tracking is one of the responsibilities of UoW. When the object is requested (SQL query) for first time, it causes round trip to database. This object is then saved in memory cache. Full ORM keeps track of changes done to this already loaded object(s). If same object is requested again (other SQL query in same UoW scope that include loaded object), they do not do database round trip. Instead, they return the object from memory cache instead. This way, considerable time is saved.
Dapper do not support this feature that causes it to perform slower in your tests.

But, this benefit is only applicable if same object(s) loaded multiple times. Also, if number of objects loaded in memory is too high, this will slow down the full ORM instead as then the time required to check the objects in memory will be higher. So again, this benefit depends on use-case.

More Related Contents:

  1. EF: Include with where clause [duplicate]
  2. Entering keys manually with Entity Framework
  3. How do I apply OrderBy on an IQueryable using a string column name within a generic extension method?
  4. The cast to value type ‘Int32’ failed because the materialized value is null
  5. LINQ To Entities does not recognize the method Last. Really?
  6. Entity framework left join
  7. What are the downsides to turning off ProxyCreationEnabled for CTP5 of EF code first
  8. An object with the same key already exists in the ObjectStateManager. The ObjectStateManager cannot track multiple objects with the same key
  9. Entity Framework 6: audit/track changes
  10. Entity Framework. Delete all rows in table
  11. “The LINQ expression node type ‘Invoke’ is not supported in LINQ to Entities” – stumped!
  12. ‘datetime2’ error when using entity framework in VS 2010 .net 4.0
  13. Entity vs Model vs View Model
  14. Eager , Lazy and explicit loading in EF6
  15. Place to put Database.SetInitializer
  16. Linq to Entity Join table with multiple OR conditions
  17. Finding the reason for DBUpdateException
  18. ‘Date’ is not supported in LINQ to Entities. Only initializers, entity members, and entity navigation properties are supported
  19. GUID COMB strategy in EF
  20. Entity framework large data set, out of memory exception
  21. entity framework update many to many relationship: virtual or not
  22. Parallel doesnt work with Entity Framework
  23. Entity Framework and multiple schemas
  24. Entity Framework Multiple Object Contexts
  25. NSubstitute DbSet / IQueryable
  26. System.Data.MetadataException: Unable to load the specified metadata resource
  27. How should I set up my integration tests to use a test database with Entity Framework?
  28. Where to convert business model to view model?
  29. Entity Framework SaveChanges() vs. SaveChangesAsync() and Find() vs. FindAsync()
  30. Entity Framework – Generating Classes

Leave a Comment