In a recent software project, we saw a big drop in the web app's performance. Here are the strategies we used to improve query performance.

Atomic Object is a software consultancy specializing in custom software development and product design. Readers can learn about software development methodologies, user-centered design principles, and agile practices. With case studies, blog posts, and technical insights, Atomic Object provides  guidance and expertise for building innovative and user-friendly software products.

Atomic Spin

In a project where PDFs were migrated from a Blob Storage container to a SQL Server database, the web app's performance dropped significantly. To address this, several strategies were used to optimize EF Core query performance: using AsSplitQuery to avoid data duplication, employing projections and DTOs for read-only data to retrieve only necessary columns, and creating indexes for frequently queried non-primary key fields. These optimizations led to a reduction in response times and overall improved performance.

Optimize EF Core Database Query Performance

Split Queries: Preventing Data Duplication

Using Projections and DTOs for Read-Only Data

Optimizing EF Core Database Query Performance

<p>Into the projection example you don’t need .AsNoTracking() because EF traces types of DbSet and when you project it into Dto so EF won’t track this object</p>
