linq-optimization-patterns

Fix the N+1 query problem in EF Core by applying eager loading with Include/ThenInclude, batch loading for cross-repository data, and DTO projection to fetch related data in a single optimized query.

The best way to optimize slow LINQ list endpoints is to use DTO projection to avoid loading full entities, batch loading to prevent N+1 queries, and efficient pagination with CountAsync before applying pagination filters.

AsSplitQuery prevents performance degradation by splitting a single large query into multiple smaller SQL queries, avoiding the Cartesian explosion that occurs when eagerly loading multiple related collections in EF Core.

Yes, you can optimize cross-repository data access in ABP Framework by implementing batch loading patterns, which consolidate per-item queries into a single optimized query to prevent N+1 issues.

Project to a DTO instead of using Include/ThenInclude when you need to improve read performance for list endpoints and dashboards by avoiding loading full entities, fetching only the necessary fields directly.

Call CountAsync before pagination to efficiently compute the total record count with optional filters applied, ensuring your pagination logic returns accurate totals without executing redundant database queries.