Entity Framework - what's the difference between using Include/eager loading and lazy loading?

entity-framework lazy-loading eager-loading
Major Productions picture Major Productions · Aug 17, 2010 · Viewed 11.4k times · Source

I've been trying to familiarize myself with the Entity Framework. Most of it seems straight forward, but I'm a bit confused on the difference between eager loading with the Include method and default lazy loading. Both seem like they load related entities, so on the surface it looks like they do the same thing. What am I missing?

Answer

Kevin Pang picture Kevin Pang · Aug 17, 2010

Let's say you have two entities with a one-to-many relationship: Customer and Order, where each Customer can have multiple Orders.

When loading up a Customer entity, Entity Framework allows you to either eager load or lazy load the Customer's Orders collection. If you choose to eager load the Orders collection, when you retrieve a Customer out of the database Entity Framework will generate SQL that retrieves both the Customer's information and the Customer's Orders in one query. However, if you choose to lazy load the Orders collection, when you retrieve a Customer out of the database Entity Framework will generate SQL that only pulls the Customer's information (Entity Framework will then generate a separate SQL statement if you access the Customer's Orders collection later in your code).

Determining when to use eager loading and when to use lazy loading all comes down to what you expect to do with the entities you retrieve. If you know you only need a Customer's information, then you should lazy-load the Orders collection (so that the SQL query can be efficient by only retrieving the Customer's information). Conversely, if you know you'll need to traverse through a Customer's Orders, then you should eager-load the Orders (so you'll save yourself an extra database hit once you access the Customer's Orders in your code).

P.S. Be very careful when using lazy-loading as it can lead to the N+1 problem. For example, let's say you have a page that displays a list of Customers and their Orders. However, you decide to use lazy-loading when fetching the Orders. When you iterate over the Customers collection, then over each Customer's Orders, you'll perform a database hit for each Customer to lazy-load in their Orders collection. This means that for N customers, you'll have N+1 database hits (1 database hit to load up all the Customers, then N database hits to load up each of their Orders) instead of just 1 database hit had you used eager loading (which would have retrieved all Customers and their Orders in one query).

Related questions

EF: Lazy loading, eager loading, and "enumerating the enumerable"

I find I'm confused about lazy loading, etc. First, are these two statements equivalent: (1) Lazy loading: _flaggedDates = context.FlaggedDates.Include("scheduledSchools") .Include ("interviews").Include("partialDayAvailableBlocks") .Include("visit").Include("events"); (2) Eager loading: _flaggedDates = context.FlaggedDates; In other words, in (1) the "Includes" …

Read More
Entity framework linq query Include() multiple children entities

This may be a really elementry question but whats a nice way to include multiple children entities when writing a query that spans THREE levels (or more)? i.e. I have 4 tables: Company, Employee, Employee_Car and Employee_Country Company …

Read More
Entity Framework: How to disable lazy loading for specific query?

Is there any way to disable lazy loading for specific query on Entity Framework 6? I want to use it regularly, but sometimes I want to disable it. I'm using virtual properties to lazy load them.

Read More