Comparison of Entity Structure Data Loading Strategy

I am reading a book Programming Entity Framework: DbContext, and I just read a chapter on three types of data loading:

  • Lazy loading (default)
  • Unwanted loading
  • Explicit loading

Now I ask myself which data loading is better in this situation. A concrete comparison would be nice! I did not find.

For example, I use the default lazy loading for the module for the client. This module applies to sales representatives and includes these related tables:

  • Reps
  • Reps_Zones
  • Reps_Prerequisites
  • Users
  • Reps_Languages
  • and etc.

In the module, I use all these tables to send appointments (about 150 appointments up to 50 repetitions at a time), but it is slow. Will using a different download strategy really improve performance?

+3
1

Lazy-loading . , , . DBcontext , , datalayer, .

Lazy loading , , , , , .

Lazy loading , , , . ToList() EF-, .

+2

All Articles