#29620: Document possible performance benefits from transactions
-----------------------------------------+------------------------
Reporter: WGH | Owner: nobody
Type: Uncategorized | Status: new
Component: Documentation | Version: 2.0
Severity: Normal | Keywords:
Triage Stage: Unreviewed | Has patch: 0
Needs documentation: 0 | Needs tests: 0
Patch needs improvement: 0 | Easy pickings: 0
UI/UX: 0 |
-----------------------------------------+------------------------
Currrently, the documentation says:
> 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 if you’re using atomic() in long-running
processes, outside of Django’s request / response cycle.
I think it's misleading, as it sounds like transactions are always bad
from performance perspective, and autocommit mode is better. While in fact
batching DB operations in transactions can have serious speedup,
especially when inserting massive amounts of rows. (of course it may have
impact on concurrency, but there ain't no such thing as a free lunch)
--
Ticket URL: <https://code.djangoproject.com/ticket/29620>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/django-updates/047.c80e241fb71ab6323400910e58f3d1eb%40djangoproject.com.
For more options, visit https://groups.google.com/d/optout.
