Support opting out of wrapping database operations in a transaction during SaveChanges() #6339
Labels
closed-fixed
The issue has been fixed and is/will be included in the release indicated by the issue milestone.
type-enhancement
Milestone
Comments
ajcvickers
added a commit
that referenced
this issue
Aug 25, 2016
…uring SaveChanges() Issue #6339 ```C# context.Database.AutoTransactionsEnabled = false; ``` Doesn't affect anything done with UseTransaction or BeginTransaction--only prevents EF from creating a transaction automatically. Also some perf improvements for running the transaction tests--previously when running on my machine they would take about 70 seconds. Now they take about 3. But note that most of this is masked when running many tests in parallel.
ajcvickers
added a commit
that referenced
this issue
Aug 25, 2016
…uring SaveChanges() Issue #6339 ```C# context.Database.AutoTransactionsEnabled = false; ``` Doesn't affect anything done with UseTransaction or BeginTransaction--only prevents EF from creating a transaction automatically. Also some perf improvements for running the transaction tests--previously when running on my machine they would take about 70 seconds. Now they take about 3. But note that most of this is masked when running many tests in parallel.
ajcvickers
added a commit
that referenced
this issue
Sep 2, 2016
…uring SaveChanges() Issue #6339 ```C# context.Database.AutoTransactionsEnabled = false; ``` Doesn't affect anything done with UseTransaction or BeginTransaction--only prevents EF from creating a transaction automatically. Also some perf improvements for running the transaction tests--previously when running on my machine they would take about 70 seconds. Now they take about 3. But note that most of this is masked when running many tests in parallel.
ajcvickers
added
the
closed-fixed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Wrapping all database operations in a transaction during
SaveChanges()is important to keep data in the database consistent and we should always do it by default. However for certain applications trading off data consistency for a performance gain may be acceptable. Some testing performed in https://github.com/aspnet/benchmarks has shown that the performance gain can be significant.The text was updated successfully, but these errors were encountered: