Home/ Questions/Q 582125
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-13T14:39:13+00:00

I hear a lot about performance problems about lazy loading, no matter if at

  • 0

I hear a lot about performance problems about lazy loading, no matter if at NHibernate, Linq….

The problem is N+1 selects. Example, I want all posts and its users, at foreach I lazy Load Users, them I need one select for posts, plus N select for each user.

Lazy Loading:

1 – select ....from post

N – select ....from user

The “good” approach is do a join:

1 – select .....from post inner join user on post.UserId = user.Id

But seeing EF generated SQL, I realized that a lot of data is wasted. Imagine that all posts are the same User. Inner Join will bring all users columns for each post row.

In performance, which approach is best?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    Lazy loading is neither good nor bad. See this for a more lengthy explanation:

    When should one avoid using NHibernate's lazy-loading feature?

    In general, lazy loading is a good default behavior for an ORM, but as an ORM user you need to be conscious of when to override the default and load data eagerly. Profiling the performance of your application is the best way to make decisions about using lazy loading or not using it. Be wary of spending too much effort on premature optimization.

    • 0