why dapper ORM is so fast by comparing Entity Framework and ADO.NET?
Multi tool use
why dapper ORM is so fast by comparing Entity Framework and ADO.NET?
Please mention the reason of Fast execution of dapper ORM by comparing Entity Framework and ADO.NET. I got the reference for comparison from the link dapper vs entity framework
I have gone through this link exceptionnotfound.net/…. it says dapper is faster than ADO.NET. Why dapper is so fast than ADO.NET even though dapper is written over ADO.NET?
– Muruga
Jan 16 at 10:28
The test is unfair because it's using
DataTable and DataAdapter.– Ivan Stoev
Jan 16 at 11:09
DataTable
DataAdapter
Have you run your own tests on your own data? Even though I'm rooting for Dapper here, EF have made really good improvements over the last few versions.
– Marc Gravell♦
Jan 16 at 15:31
Dapper is faster than EF Core, which is faster than EF, all on latest versions, on my recent tests for my app. But EF Core has major improvements and it really fast indeed.
– Anderson Matos
Jan 16 at 15:36
1 Answer
1
It can never happen that Dapper is much faster than ADO.Net. Period!
We know that Dapper team has written an advance mechanism via IL to just speed-up the process, but still it is running on top of ADO.Net. They are only abstracting the ADO.Net and processed everything on top of it by converting the actual data (rows) back to the object models (POCO or DTO), and that would add additional time doing it.
I think everyone must understand the separation of concern of the ADO.Net layer from any other ORM available on this world.
Or else or unless, the Dapper team will write their own version of DbDataReader, then, there could be a possibility that they are much faster, but never ever it will happen until they do it.
With EF, there is no question that Dapper is much faster than it as they are the most lightweight ORM right now that is available.
IMHO
They are more lightweight as they have the most minimum lines of code being processed during the runtime.
– Michael Pendon
Jul 3 at 8:40
By clicking "Post Your Answer", you acknowledge that you have read our updated terms of service, privacy policy and cookie policy, and that your continued use of the website is subject to these policies.
First, nothing can be faster than ADO.NET because all frameworks use ADO.NET internally. Second, you are comparing apples and oranges, because Dapper is micro ORM while EF is full ORM, hence supports much complex scenarios, which of course have asociated overhead. Dapper requires SQL knowledge, EF - does not. etc.
– Ivan Stoev
Jan 16 at 10:11