Don't SUCK With Entity Framework - Change Tracking - Performance Tips Part 8

preview_player
Показать описание

► Part 8 - Change Tracking - THIS VIDEO

In this video series, you will learn the most common performance mistakes developers do with Entity Framework. In the eighth part, I show how to disable change tracking when you don't need it.

★★ BECOME A BACKER OR SPONSOR ★★
▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬

★★ Follow My Tested ASP.NET ★★
▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬

★★ Follow Me ★★
▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬

★★ Links From The Video ★★
▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬▬
► BenchmarkDotNet:
Рекомендации по теме
Комментарии
Автор

Maybe it is better to create a constructor for db context with Boolean parameter defaulted to true, and change the tracking based on that? Or "false" - whatever is your most common use case.

gralexp
Автор

Thank you so much sir. This was really helpful 🤠

incnito
Автор

Another great video from the "Dont SUCK with EF" series thanks Ivo :)
I think it would've been good to mention some real life cases (based on your knowledge/experience) in which we can benefit from turning of the "Change Tracking".

From my personal experience I can say that maybe a good place to disable EF Change Tracking will be in case you have splitted your database to write and read replicas and you use different EF contexts for each, then it seems logical to disable Change Tracking on the read replica, wdyt?

KrisLyubenov