4 ms·
We are also running into more and more performance issues with EF. There are ways to tune it but I am not sure if it’s worth learning this for EF or if it’s not
by vjvjvjvjghv 11mo ago
We are also running into more and more performance issues with EF. There are ways to tune it but I am not sure if it’s worth learning this for EF or if it’s not better to just go for straight SQL. Seems MS has this tendency to create abstractions that then don’t work 100%. I see this with .NET too. Often you have to go down to Win32 for apps that are tightly coupled with Windows and hardware.
- Limeray 11mo ago[dead]
- oaiey 11mo agoIs not that the core problem with ORMs. All of them. In the end you do straight SQL when it comes to Performance.
- littlecranky67 11mo agoAre you talking about EF or EF Core? If the later, did you enable any or all of the magic like automatic property evaluation/eager fetching etc.? EFCore by default is pretty performant - and pretty basic. You need to manually .Include() joins etc. which makes it pretty hard to become slow.
- vjvjvjvjghv 11mo agoEF Core. It’s fine to some degree but larger queries with lots of joins can get very slow. Not all but just some of them.