-
Notifications
You must be signed in to change notification settings - Fork 10
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
[Research] Performance Split Queries #410
Comments
Please note that this feature was introduced in EF Core 5.0 and DeX is running version 3.1 |
It should be possible to update EF Core to 5.0 maybe it is also worth it to look into that. AsNoTracking should be looked into for sure. I think it will only cause issues for deletes since the Update method that entity framework has does not look at deleted entities. |
Definitely, although it will also require you to upgrade .NET Core 3.1 (LTS) to .NET 5 (no LTS) on all projects. This is a significant upgrade... |
Didn't think about LTS thats maybe not a good plan then. |
Not running LTS is not a significant issue if you are actively developing the product(DeX is still being actively developed). Research should be done to see if it is worth it to update to .NET 5, and later this year to .NET 6 (LTS), in terms of time vs gains. |
Btw i don't think you have to upgrade to .net 5 to use this functionality. ASAM uses ef 5.0.1 and is version .net core 3.1. But it could be different for Dex maybe. |
Is your feature request related to a problem? Please describe.
Split queries maybe could help to improve the performance.
https://docs.microsoft.com/en-us/ef/core/querying/single-split-queries
Describe the solution you'd like
Investigate the difference between performance of split and single queries.
Production URL
Additional context
The text was updated successfully, but these errors were encountered: