Hunting the N+1 Query Problem with a Roslyn Analyzer
Most collection-related performance advice stops at the method boundary: avoid redundant ToArray() calls, pre-size your List<T>, swap a linear Contains() scan for a HashSet<T>. Those micro-optimizations matter, but they pale in comparison to a much bigger and much more common mistake — the N+1 Query Problem.
Harmful collection transformations. Part 2: automatic diagnostics
The previous post contains code examples that can be simplified by removing ToArray() or ToCharArray() calls. And an interesting example with List<char> constructor. But we need to be very attentive to find such places in our code. It would be much safer to do it automatically. This post shows us about automatic compiler diagnostics that can detect issues.
Csharp (32)
.net (26)
performance (14)
benchmark (13)
LINQ (12)
MSSQL (7)
.net48 (6)
.netcore31 (6)
.net6 (5)
.net8 (5)
TSQL (5)
collections (4)
string (4)
patterns (4)
.net9 (4)
.net10 (3)
regex (3)
roslyn (2)
analyzer (2)
list (2)
dapper (2)
sql (2)
specification (2)
repository (2)
EntityFramework (2)
.net5 (2)
optimization (2)
.net471 (2)
stackoverflow (2)
retry (2)
circuit breaker (2)
AutoMapper (1)
plugin (1)
ReSharper (1)
Rider (1)
HashSet (1)
whitespaces (1)
paging (1)
NDepend (1)
asp.net (1)
xml (1)
soap (1)
CancellationToken (1)
Timer (1)
debug (1)
properties (1)
IEnumerable (1)
foreach (1)