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
Microsoft.EntityFrameworkCore.SqlServer 9.0-rc2 downgraded the Microsoft.Data.SqlClient to 5.1.6 where the latest version is 5.2.2 and causes way more memory allocation and decreasing performance, the rc1 version was ok.
As I'm preparing for my talk on .NET Conf 2024 and the main idea is about investigating this long-term bug dotnet/SqlClient#593, here is the benchmark result for EF Core 9.0 rc1 and rc2.
Feel free to reference the newer version, but EF Core only use LTS versions of SqlClient due to past bad experience of non LTS going out of support before the EF Core version
@ErikEJ Ok thank for the point for using LTS version of SqlClient, but I wonder why for a EF version which is not a LTS we need to use a LTS version of internal package, I know SqlClient is an exception but still.
Microsoft.EntityFrameworkCore.SqlServer 9.0-rc2 downgraded the
Microsoft.Data.SqlClient
to5.1.6
where the latest version is5.2.2
and causes way more memory allocation and decreasing performance, the rc1 version was ok.As I'm preparing for my talk on .NET Conf 2024 and the main idea is about investigating this long-term bug dotnet/SqlClient#593, here is the benchmark result for EF Core 9.0 rc1 and rc2.
Benchmark Code
Result for EF Core 9.0-rc1 using SqlClient 5.2.2 internally:
And Result for EF Core 9.0-rc2 using SqlClient 5.1.6 internally:
Thankfully, we still have time to patch for the EF Core 9.0 stable version.
EF Core version: 9.0.0-rc.2.24474.1
Database provider: Microsoft.EntityFrameworkCore.SqlServer
Target framework: .NET 9.0
Operating system: Windows 11
The text was updated successfully, but these errors were encountered: