What is the difference between lazy loading and eager loading

With Lazy Loading, we only retrieve just the amount of data, which we need in a single query. When we need more data related to the initial data, additional queries are issued to the database.

This means there are several round trips between the Application Server and the database Server. In general, these database round trips are very often the major performance bottleneck in most Applications.

Lesser the round trips, better will be the performance. For example, if on a given page, you are only displaying Departments, then there is no reason for Eager Loading related Employees data.

Hence, in this case, Lazy Loading works best. On the other hand, if you are displaying both Department and Employees data, then Eager Loading works best, as it avoids the additional round trips to the database. View All. Akshay Phadke Updated date Jul 05, Now, we also want to log the SQL query, which is generated on the console screen and to do this, we are going to make use of LOG property of the data context object. Thus, we had written columns, which we want to display, followed by boundfield control and specify the header text.

Thus, within the page, load an event and create an instance of SampleDatacontext. Basically, we are telling along with department entites. This anonymous type is going to have a name property and the value of the name is going to be department object.

Thus, it means that we have one select for the Departments, and then N additional selects to retrieve the employees belonging to each Department, where N is the total number of Departments.

Next Recommended Reading. Windows 10 Vs Windows Visual Studio Vs Visual Studio Understanding Matplotlib With Examples. Understanding Numpy With Examples. C Evolution. Note: like Transcendent said there may be disposal problem with lazy loading. Improve this answer. I wast just trying to answer the same thing. Use lazy loading when you know you will rarely need to use the related data.

But when you know you will want certain related data quite often, use eager loading. When to use: Use Eager Loading when the relations are not too much. Thus, Eager Loading is a good practice to reduce further queries on the Server. Use Eager Loading when you are sure that you will be using related entities with the main entity everywhere.

When to use: Use Lazy Loading when you are using one-to-many collections. Use Lazy Loading when you are sure that you are not using related entities instantly. Dark Matter Dark Matter 1, 1 1 gold badge 23 23 silver badges 31 31 bronze badges. I'm really confused about eager and lazy loading. By reference of google i fould this thing about lazy loading. Jan 7, " is that the same thing that you said about lazy loading. You can refer from here for better understanding: Eager Loading - entityframeworktutorial.

Both approaches have their benefit, lazy loading can avoid loading unused data, but eager loading minimizes the trips to the database. Flater Thank you so much. I'm not gonna forget that anymore. Transcendent Transcendent 5, 4 4 gold badges 20 20 silver badges 46 46 bronze badges. Yes, that is example when Lazy Loading does not help. Another thing is that creating DbContext everytime you will need some data is bad way. MiroslavHolec: Brilliant, that's what I actually do using Ninject.

What you just mentioned is indeed very very nice. Sheriff Sheriff 6 6 silver badges 18 18 bronze badges. After that, you can fetch the related objects with the parent object in one query itself. Eager loading In case of eager loading, related objects child objects are loaded automatically with their parent object.

To use Eager loading you need to use Include method. With Eager Loading, all the data is retrieved in a single query, which can then be cached to improve the Application performance. With Eager Loading, we are trading memory consumption for the database round trips. I would like to have feedback from my blog readers. Request demo Learn more. Article's content. Latest Blogs. Data Security Application Delivery. Bob Bentley. Industry Perspective Application Delivery Data Security Engineering.

Nanhi Singh. Application Security