Menu
I used dapper.net as micro-orm, speed and performance is fantastic.
Simple CRUD Operations in Dapper is more quickly than Entity Framework 6.
Speed-Comparison-Dapper-vs-Entity-Framework
But if I want speed and performance of Entity Framework 6 like Dapper, what should I do?
I do not need all the advanced features of Entity Framework 6 so
Can I disable some features to increase speed and performance of Entity Framework 6? Which one?
Which features are costly and increase the speed to disable them? (Please specify)
363
Dapper is literally much faster than Entity Framework Core considering the fact that there are no bells and whistles in Dapper. It is a straight forward Micro ORM that has minimal features as well. It is always up to the developer to choose between these 2 Awesome Data Access Technologies.
But the answer to your question is Yes, Dapper is quicker than EF Core for reading data. And it probably always will be, because it is not a full blown ORM like EF Core. It is a simple object mapper and designed specifically to be quicker than EF Core for reading data.
NHibernate is still faster than ADO and Dapper for everything except the select.
Simple CRUD Operations in Dapper is more quickly than Entity Framework 6.
Yeah. So what? EF is known to be slow. Deal with it. It is documented and a work item they hope to work on some point before EF 100. They got faster already but they still are slow.
But if I want speed and performance of Entity Framework 6 like Dapper, what should I do?
1: use Dapper.
Or:
2: sit down with the EF source code and fix the issues and submit it as a patch.
Can I disable some features to increase speed and performance of Entity Framework 6 ?
Entity Framework is Too Slow. What are my options?
111
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
