Reputation: 21764
We have a rather large EF code-first model that takes a long time to spin up. With EF5 & pre-compiled views, the load time was 30-45 seconds. However, after upgrading to EF6.1, the load time is > 3 minutes. All of this work is happening before it even starts looking at the precompiled views.
By pausing the debugger, I determined that nearly all time is being spent calling SequenceEqual inside the anonymous function created by TablePrimitiveOperations.GetPropertyPathMatcher (see the source). Using a profiler, I've confirmed that over 80% of the time is being spent in this method.
Are there any known fixes to this issue? I've posted it on Connect but I'm wondering if there's a workaround available currently.
Upvotes: 4
Views: 326
Reputation: 21764
It turns out this is an actual bug in EF 6.1.0. MSFT has created a fix which is available in the 6.1.1 beta and will be available in the 6.1.1 release.
Upvotes: 2