From 189fb4e29463a2e1ee1a86a6c29c94f9f9904d6f Mon Sep 17 00:00:00 2001
From: Aymeric Augustin <aymeric.augustin@m4x.org>
Date: Thu, 7 Mar 2013 23:06:58 +0100
Subject: [PATCH] Added a note about long-running processes.
There isn't much else to say, really.
---
docs/topics/db/transactions.txt | 7 +++++++
1 file changed, 7 insertions(+)
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
==========