Performance
Is it any performance characteristics of using ADO.NET vNext and LINQ in cotrary with ordinary ADO.NET, database views or ADO.NET vNext without LINQ?
Thank you
Is it any performance characteristics of using ADO.NET vNext and LINQ in cotrary with ordinary ADO.NET, database views or ADO.NET vNext without LINQ?
Thank you
Hi,
The Entity Framework and LINQ integration, just like any other higher-level abstraction, introduces certain amount of overhead to the system. So typically you can expect it to be somewhat slower than using the lower-level ADO.NET APIs directly (e.g. datareader). Given that productivity and expressivity gains, this trade-off typically works well.
The August CTP did not include most of the performance work that we're planning to do to make sure performance is at an appropriate level. In future iterations we'll include more of the performance optimizations we're working on and you should see performance going up considerably.
Regarding the overhead of LINQ to Entities compared to using the Entity Framework with Entity SQL, we're still analyzing the perf characteristics of each one, but you can expect that the difference should be very, very small, if any.
Pablo Castro
ADO.NET Entity Framework
Microsoft Corporation
Is there even the vaguest roadmap for these future iterations? And is final release scheduled for 2007? 2008?
Also, have you guys ever thought of moving even more towards a cvs/subversion type model where people outside Microsoft could see/use the latest and greatest bits, between even CTP releases ?
I'm pretty sure there would be others interested in that.
Thanks.
jdn