4 ms·
Not sure which version of EF those benchmarks are using, or how representative it is. For what it's worth, the EF team has been focusing on performance for EF5
by Smudge 14y ago
Not sure which version of EF those benchmarks are using, or how representative it is. For what it's worth, the EF team has been focusing on performance for EF5 and is making some promising improvements:
http://blogs.msdn.com/b/adonet/archive/2012/02/14/sneak-preview-entity-framework-5-0-performance-improvements.aspx http://blogs.msdn.com/b/adonet/archive/2012/02/14/sneak-prev...
(Disclosure: I work at Microsoft)
- mythz 14y agoThe benchmarks are from StackOverflow's Open sourced Dapper ORM project - the source of which is contained in their repo: http://code.google.com/p/dapper-dot-net/ http://code.google.com/p/dapper-dot-net/
- mythz 14y agoIf you guys are so "open" why aren't your performance advances compared in context against other ORMs? Benchmarks means a lot more in context and are more meaningful when they're compared to alt fx's on the same hardware specs / RDBMS / network configuration, etc. But I guess it doesn't matter when you're still be the most popular .NET package http://nuget.org/packages http://nuget.org/packages (580k) whilst remaining more than a factor of times slower than the competition - that's the .NET OSS ecosystem for you.