You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
My question: Is there any plans to use Source Generators in EF to improve the performance?
And if there is any, When?
Just a wild idea, imagine that LINQ Query on DbContext generates ADO.NET code of the SQL Query and map it to the class (at compile time without reflection)
Would not that be great for the performance of EF, even maybe surpass the performance of Dapper?
I searched the issues before opening this one, and I found nothing,
Sorry if there is an already opened issue for this
Thank you all
The text was updated successfully, but these errors were encountered:
@stephentoub has shown great uses cases of source generators in .NET 7 to improve the performance dramatically.
https://www.youtube.com/watch?v=rwfNDyBBgks
My question: Is there any plans to use Source Generators in EF to improve the performance?
And if there is any, When?
Just a wild idea, imagine that LINQ Query on DbContext generates ADO.NET code of the SQL Query and map it to the class (at compile time without reflection)
Would not that be great for the performance of EF, even maybe surpass the performance of Dapper?
I searched the issues before opening this one, and I found nothing,
Sorry if there is an already opened issue for this
Thank you all
The text was updated successfully, but these errors were encountered: