-
Notifications
You must be signed in to change notification settings - Fork 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
Performance Guidance #212
Comments
Any progress on this? In particular looking for SQLite+UWP perf tips. |
@bartlannoeye the perf issues in UWP/SQLite are bugs that we're working with the .NET Native team to address. Unfortunately there isn't really any way to work around them. |
Putting this on the backlog. A lot of the perf guidance from EF6 doesn't really apply to EF Core and I'm not sure how much we need to document here. I think it probably makes sense to wait a bit longer and see what kind of things aren't obvious to most folks, and then document these. |
@divega a Short perf doc would be beneficial and would surely grow as customers contributed their perf findings. dotnet/AspNetCore.Docs#964 has a short EF perf section. It would be better to move that section to this repo and the ASP.NET Core perf doc could point to it. |
@Rick-Anderson The short EF section I read in the PR seems like a good start of a page on the EF Core side. I posted some comment that hopefully can make it better. There a few things remaining here that of course also have value, although at this point I think I would leave the "Key generation: sequence vs identity" part out. |
But isn't Rowan correct
|
@Rick-Anderson yeah, this should be reviewed case-by-case, lots of things are relevant, some probably aren't... This is one of the major docs tasks on my plate. |
Closes dotnet#212 Closes dotnet#2608
Some things already mentioned in various docs. Would be nice to have one doc dedicated to all the perf tips.
Some ideas:
The text was updated successfully, but these errors were encountered: