-
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
Regression in single context creation perf #19864
Comments
Suspected commit according to meeting https://github.com/dotnet/efcore/pull/19517/files Does initializing context also initializes DbSets even if not used? |
@smitpatel That's pretty much the only thing that happens before a context is used https://github.com/dotnet/efcore/blob/master/src/EFCore/DbContext.cs#L112 |
And if we can confirm that #19517 caused it we don't have or really can fix it |
Should be really easy to simply run the benchmark on the cmdline on both commits to check (let me know if you run into trouble). |
Seems like @roji is volunteering to verify the commit for regression. |
That was not quite the semantic content of my message... however: Before change (f98509f)BenchmarkDotNet=v0.11.3, OS=ubuntu 19.10
Intel Xeon W-2133 CPU 3.60GHz, 1 CPU, 12 logical and 6 physical cores
.NET Core SDK=3.1.100
[Host] : .NET Core 3.1.1 (CoreCLR 4.700.19.60701, CoreFX 4.700.19.60801), 64bit RyuJIT
Toolchain=InProcessToolchain
After change (dd843a2)BenchmarkDotNet=v0.11.3, OS=ubuntu 19.10
Intel Xeon W-2133 CPU 3.60GHz, 1 CPU, 12 logical and 6 physical cores
.NET Core SDK=3.1.100
[Host] : .NET Core 3.1.1 (CoreCLR 4.700.19.60701, CoreFX 4.700.19.60801), 64bit RyuJIT
Toolchain=InProcessToolchain
For reference, running is super simple has no hard dependency on @roji:
|
Oops! My mistake! 😉 |
I have ideas. |
The text was updated successfully, but these errors were encountered: