summaryrefslogtreecommitdiff
path: root/docs/topics/db/transactions.txt
diff options
context:
space:
mode:
Diffstat (limited to 'docs/topics/db/transactions.txt')
-rw-r--r--docs/topics/db/transactions.txt7
1 files changed, 7 insertions, 0 deletions
diff --git a/docs/topics/db/transactions.txt b/docs/topics/db/transactions.txt
index 4cecf896a4..8cbe0dccd0 100644
--- a/docs/topics/db/transactions.txt
+++ b/docs/topics/db/transactions.txt
@@ -164,6 +164,13 @@ Django provides a single API to control database transactions.
- releases or rolls back to the savepoint when exiting an inner block;
- commits or rolls back the transaction when exiting the outermost block.
+.. admonition:: Performance considerations
+
+ Open transactions have a performance cost for your database server. To
+ minimize this overhead, keep your transactions as short as possible. This
+ is especially important of you're using :func:`atomic` in long-running
+ processes, outside of Django's request / response cycle.
+
Autocommit
==========