EF Core 11 (since preview 3) optimizes split queries by pruning unnecessary reference navigation JOINs from collection queries. Previously, when using AsSplitQuery with both reference and collection navigations, each collection query would redundantly JOIN and ORDER BY all reference navigation tables. EF Core 11 removes these superfluous JOINs, producing leaner SQL closer to what a developer would write by hand. Benchmarks comparing .NET 10 vs .NET 11 show roughly a 9% reduction in execution time (68.5ms → 62ms) and about 10% less memory allocation (33.35MB → 30.15MB) for a dataset of 5,000 blogs with 5 posts each.

4m read timeFrom steven-giesel.com
Post cover image
Table of contents
So what is the issue?So what changed?BenchmarksResources
38.6K Impressions1 Comment