- Notifications
You must be signed in to change notification settings - Fork3.3k
[release/9.0-staging] Fix to #35239 - EF9: SaveChanges() is significantly slower in .NET9 vs. .NET8 when using .ToJson() Mapping vs. PostgreSQL Legacy POCO mapping#35360
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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.
Already on GitHub?Sign in to your account
Uh oh!
There was an error while loading.Please reload this page.
Conversation
Uh oh!
There was an error while loading.Please reload this page.
Uh oh!
There was an error while loading.Please reload this page.
…s. .NET8 when using .ToJson() Mapping vs. PostgreSQL Legacy POCO mapping
maumar commentedDec 27, 2024
@AndriySvyryd update: added changes to the cosmos StringDictionaryComparer. It does support nested collections and the legacy functions can be invoked (rather than just being constructed like in relational). I added targeted fix similar to what I initially did for main. |
AndriySvyryd commentedDec 30, 2024
Looks good. Can you add the servicing template? |
maumar commentedJan 6, 2025
/azp run |
| Azure Pipelines successfully started running 1 pipeline(s). |
2954996 intorelease/9.0-stagingUh oh!
There was an error while loading.Please reload this page.
Uh oh!
There was an error while loading.Please reload this page.
Fixes#35239
Safer version of#35326
Description
EF9 introduced a change in how we construct ValueComparers for some of our types (specifically collection of scalars/references), in preparation for AOT work. The way the change was implemented may cause a severe performance regression during SaveChanges operation involving multiple entities using collections of primitives (one of our highly requested features).
Customer impact
Customers performing data manipulation operations on entities with collections of primitives may experience significant performance regressions. This may also happen when no data has been changed, but sufficiently large entity graph has been loaded into change tracker. There is no workaround for this issue, apart from changing the model to not use primitive collections (which is unacceptable for majority of customers)
How found
Multiple customer reports on EF 9
Regression
Yes, from EF8. Note: this is a perf regression only, not a functional regression.
Testing
Ad hoc performance test using BenchmarkDotNet. Functional testing already covered by existing tests.
Risk
Low. The patch fix has been limited in scope to reduce the risk. Changes should only affect models with primitive collections. Added quirks just to be sure.
Perf numbers
Over 20x regression between 8 and 9 for the tested scenario.
8.0.11
9.0
9.0.2 (with fix)