Entity Framework Core Unchained Getting the Best Performance from Your ORM
summary
Entity Framework Core defaults cause surprises but can be tuned: enable retry on failure for cloud or serverless Azure SQL, avoid default tracking and use no tracking for read APIs to save roughly 30% memory/CPU, EF Core uses a merge for bulk inserts (efficient up to ~500 rows) and max batch size controls it, code‑first hides SQL types and indexes, complex joins and ETL perform poorly so prefer stored procedures or dapper for the absolute fastest SQL and use views/indexes designed for your access patterns.
AI-written summary · about
chapters (22)
- 0:00Start
- 0:25Configuration
- 8:26Lazy and Eager Loading
- 8:44Eager Loading
- 9:06Suggested Configuration
- 9:31Enable Retry on Failure
- 11:06Query Tracking
- 11:38Detailed Errors
- 13:18Core Events
- 14:23Relational Event Ids
- 16:47Crud
- 19:46Max Batch Size
- 24:32Updates and Deletes
- 27:24The Fastest Query You Can Run
- 33:50Sql Server Indexing
- 34:51String Indexes
- 36:40Database Design
- 37:49General Guidance
- 41:51Code First Tools
- 46:10Table Partitioning
- 48:50Parameter Issues
- 50:43Guiding Words
related talks
01h 04mCommon mistakes in EF Core
01h 00mGetting the best out of Entity Framework Core
01h 05mCommon mistakes in EF Core
01h 04mCommon mistakes in EF Core
01h 10mModern Data Applications with Entity Framework 7
47mEF Core 6: Working on the Bucket List
59mEF Core 6: Fulfilling the Bucket List
56mEntity Framework debugging using SQL Server: A Detective Story