{"id":8707,"date":"2026-05-05T07:49:38","date_gmt":"2026-05-05T07:49:38","guid":{"rendered":"https:\/\/studysection.com\/blog\/?p=8707"},"modified":"2026-05-05T07:49:38","modified_gmt":"2026-05-05T07:49:38","slug":"ef-core-lazy-loading-n1-problem-causes-and-solutions","status":"publish","type":"post","link":"https:\/\/studysection.com\/blog\/ef-core-lazy-loading-n1-problem-causes-and-solutions\/","title":{"rendered":"EF Core Lazy Loading N+1 Problem: Causes and Solutions"},"content":{"rendered":"

In Entity Framework Core, lazy loading postpones the retrieval of related entities until those properties are explicitly accessed in your application code.<\/span><\/p>\n

Example:<\/span><\/p>\n\n\n\n
var cars = context.Cars.ToList();<\/span><\/p>\n

foreach (var car in cars)<\/span><\/p>\n

{<\/span><\/p>\n

\u00a0\u00a0\u00a0\u00a0Console.WriteLine(car.Manufacturer.Name); \/\/ Manufacturer gets loaded lazily here<\/span><\/p>\n

}<\/span><\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n

 <\/p>\n

Even though you execute <\/span>context.Cars.ToList()<\/span>, EF Core issues additional queries whenever <\/span>car.Manufacturer.Name<\/span> is referenced, triggering multiple round-trips to the database<\/a>.<\/span><\/p>\n

Problem<\/b><\/h2>\n

Let\u2019s say there are <\/span>10,000 cars<\/b>.<\/span>
\n<\/span> EF will produce the following if lazy loading is enabled and every student has a related car entity:<\/span><\/p>\n