Entity Framework Core 7.0 will not wrap single changes in a transaction where possible to improve performance

Entity Framework Core 7.0 will not wrap single changes in a transaction where possible to improve performance. This is nice and the perf gain will increase as latency increases due to less roundtrips.

Another small but nice improvement by the Entity Framework team 💪🏻.


You might also be interested in...

Setting batch size in Entity Framework Core
Entity Framework (pre-core) didn’t support batching of CUD statements, so if you were inserting 100 entities for example, EF sent … Continue reading Setting batch size in Entity Framework Core...

Using split queries (AsSplitQuery) in Entity Framework Core to avoid the cartesian explosion problem
Without lazy loading in Entity Framework Core we must eagerly load related entities which means we can experience the ‘cartesian … Continue reading Using split queries (AsSplitQuery) in Entity Framework...

Improving performance of read only selects in entity framework by turning off tracking with AsNoTracking method
We had a new contractor start the other day in work and he brought to my attention the ability to … Continue reading Improving performance of read only selects in...

String.FirstOrDefault() LINQ queries now supported in Entity Framework Core 5.0
Entity Framework Core 5.0 now supports the translation of String.FirstOrDefault() LINQ queries. In EF Core 3.1 the following would fail… … Continue reading String.FirstOrDefault() LINQ queries now supported in Entity...

Filtered includes now supported in Entity Framework Core 5.0
Filtered includes is an awesome new feature in Entity Framework Core 5.0 which was released in November 2020. Without lazy … Continue reading Filtered includes now supported in Entity Framework...

Leave a Reply

Your email address will not be published. Required fields are marked *