-
Notifications
You must be signed in to change notification settings - Fork 3.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Perf regression in EF #16405
Comments
@roji Please add this to your existing perf work this week. |
Note that not all of those scenarios are EF, some use raw ADO.NET, and others use Dapper. So whatever's caused this is affecting all variants, not just EF. |
Where is the source code for those tests? |
The regression seems to have disappeared: It's pretty weird: the drop only shows on Linux+Physical, the others are pretty flat. It's also odd for only SingleQuery to regress, across raw/dapper/EF, but no other DB benchmarks to show anything. I'd put my money on some unrelated environmental thing (some process inadvertently running at the same time as the benchmark?), but let's follow closely. Closing for now unless anyone has any objections. |
One more important note (@smitpatel and others): the TechEmpower tests are pinned to preview5 of EF Core, since we're running with Npgsql which does not constantly follow master branch - so nothing we currently do in EF Core would actually show up here. We do have the newish EF Core microbenchmarks tab in PowerBI which does follow continuous EF Core perf. I typically sync up Npgsql every preview release, but didn't do it for preview6 (plan to do so for preview7 as soon as that's released). |
It seems a change went in today and regressed the Single Query performance for all the EF-involved scenarios:

The text was updated successfully, but these errors were encountered: