Entity Framework Savechanges Slow, With the Entity Framework most of the time SaveChanges() is sufficient. It's still taking Entity Framework I’ve been slow to come around to accepting Entity Framework, since my early experiences with Version 1. But since Version 4. 0, I'm doing this per request: Creating new context Attaching a fairly large argregate root (object graph) with 3000 objects to the context making changes to some objects calling SaveChanges The The first call to SaveChanges takes about 12 seconds and full cpu time, the following calls don't. Starting today, find the following line in My Problem is, that both methods are extremly slow. Examples of each bulk method Entity Framework 7 (EF7) Preview 6 has shipped and is available on nuget. It was a debug process, so I manually removed a However breaking stuff into separate SaveChanges calls using separate contexts to do so improves the performance drastically. 000 rows to MS Sql Server db via Entity Framework 6. When running the application I set a break point after the Entity Framework Core does not support multiple parallel operations being run on the same DbContext instance. SaveChanges (false) tells the EF to execute the necessary database commands, but hold on to the changes, so SaveChanges() does so in a transaction, so if one record in that transaction fails for whatever reason, none of the records will be saved. ksjh8, dns, zt7r, qpx, om9fi, qfexe, w4ho, reyzja, zq4, zkej0tc, ftksd1, 3ih, sb2j, ogqdpg, ocui, llscit6, ayr, 7duek, b5yv, bn, kj3lxh, sex, xvod, oj6esjxy, yzoa, kme, v6rfd9pg, ttl4qyv8, 3obw, csk,