Struggling with slow EF Core operations?
With ZZZ Projects’ EF Core Extensions, you can boost performance like never before.
Experience up to 14× faster Bulk Insert, Update, Delete, and Merge — and cut your save time by as much as 94%.
https://entityframework-extensions.net

Your EF Core app is making 1501 SQL queries per request - and the code looks completely fine. In this video I'll show you exactly why the N+1 problem happens, what cartesian explosion is, and the three fixes that will save your database.

We cover lazy loading and why it's disabled by default in EF Core, projection and when it stops working, eager loading and the cartesian explosion trap, and AsSplitQuery as the fix for multiple collection includes.

All fixes are demonstrated in a real ASP.NET Core Minimal API project with SQL Server and EF Core in .NET 10 - with full SQL output visible so you see exactly what hits your database at every step.

📌 What you will learn:
- Why lazy loading silently fires 1501 queries per request
- Why projection with collections causes the same problem as eager loading
- How AsSplitQuery eliminates cartesian explosion with one word

📬 .NET Newsletter: https://lnkd.in/drjE3rjP
🎨 Patreon [SOURCE CODE]: https://www.patreon.com/remigiuszzalewski
💼 LinkedIn: https://www.linkedin.com/in/remigiusz-zalewski

✅ Don't forget to like, subscribe, and comment your questions!

#dotnet #efcore #aspnetcore #csharp

We Are .NET

A practical walkthrough of two major EF Core performance pitfalls: the N+1 query problem and Cartesian explosion. Starting with a demo showing 1,501 SQL queries and 7.5-second response times caused by lazy loading, the tutorial covers three approaches to loading related entities: projections (best for scalar/aggregate data, risky with collections), eager loading with Include (causes Cartesian explosion with multiple collections), and split queries using AsSplitQuery() (reduces response from timeout/15s down to ~700ms by issuing separate SQL statements instead of joining everything into one massive result set). Key takeaways: disable lazy loading proxies, use projections for single nav properties and aggregates, and use split queries when loading multiple collection navigations.

EF Core Performance: N+1, Cartesian Explosion and How to Fix Both